{"id":"AGT-008","section":"Agent & MCP Governance","requirement":"Support local and remote MCP gateway placement for employee AI clients","acceptance":"Support applicable Windows, macOS and Linux patterns, allow endpoint-integrated or remote placement, and define traffic coverage for each.","tier":"AT3, AT4, AT6","whyItMatters":"Different MCP clients need different gateway placements to be covered.","verificationMethod":"W + D","verificationTest":"The vendor shows local and remote MCP gateway placement and documents what each covers.","formerly":"ARC-005","alsoIn":[],"sort":43,"adoptionContext":"Citizen-built, code-executing and MCP-extended workflows motivate local or remote gateway placement; these contexts do not necessarily involve agent-to-agent communication.","mappings":[{"frameworks":["rmf"],"explanation":"Documented MCP gateway placement identifies where component controls can operate and which traffic they cover. It supplies architecture evidence rather than proof of effective authentication or inspection.","kind":"framework","references":{"rmf":["MAP 4.2"]},"relation":null,"conditions":[]},{"frameworks":["iso"],"explanation":"Operating-system patterns, local or remote gateways and their dependencies provide computing-resource information for AI deployment. Availability of placement options does not establish secure operation.","kind":"framework","references":{"iso":["A.4.5"]},"relation":null,"conditions":[]},{"frameworks":["owasp"],"explanation":"An MCP gateway’s location and coverage can establish an inspection boundary for runtime-fetched servers and other agentic supply-chain components. Placement alone neither assesses their trustworthiness nor prevents malicious components.","kind":"framework","references":{"owasp":["ASI04"]},"relation":null,"conditions":[]}],"area":"Agent & MCP Governance","areaSlug":"AGT","url":"/r/AGT-008","frameworkRefs":{"ISO42001":["A.4.5"],"NIST-AI-RMF":["MAP 4.2"],"OWASP-ASI":["ASI04"]}}