| Framework Home | Research Index | Cross-Pillar Governance | AISM | NEXUS | Dashboard |
Current framework context: AI SAFE² v3.1. This research note preserves its original publication date, evidence, and historical framework references. Use current v3.1 normative control and profile documents for implementation or conformance decisions.
| Framework Home | Cross-Pillar Governance | AISM | NEXUS | Research 023 |
Current revision: August 2026
Historical origin: April 2026 consumer-protection research
Current profile: CP.5.MCP v3.1, MCP-1 through MCP-19
MCP consumers face a different problem from MCP server operators. A consumer may connect an agent to a server it does not control, cannot inspect continuously, and cannot assume will preserve the same tool catalog, authorization behavior, or returned-content integrity over time.
Consumer-side defenses therefore remain necessary even when the server claims to be secure.
AI SAFE² v3.1 extends the original consumer threat model to MCP 2026-07-28, with particular emphasis on returned-content trust, catalog drift, state-handle misuse, replay, intended-resource/audience validation, and SSRF boundaries.
A compromised server may continue returning apparently correct tool results while exfiltrating data, mutating behavior, or introducing malicious content. Functional correctness is not evidence of server integrity.
Relevant controls: MCP-2, MCP-4, MCP-5, MCP-9, MCP-11.
A previously trusted server may change tools, descriptions, schemas, or extensions. The consumer needs a provenance baseline and a revalidation policy rather than assuming that a familiar endpoint still represents the same authority surface.
Relevant controls: MCP-11, MCP-14, MCP-18.
Tool loops, retries, or excessive downstream work create economic exposure for the consumer even when the remote server is not intentionally malicious.
Relevant control: MCP-8.
A credential valid somewhere is not necessarily valid for the intended MCP resource. Consumers and gateways must avoid cross-resource token reuse and validate intended-resource/audience binding where applicable.
Relevant control: MCP-19.
A malicious tool response can affect future behavior if it is written into governed memory. v3.1 describes persistence using request, handle_scoped, and durable scopes rather than treating a protocol session as the governance boundary.
Relevant controls: MCP-2, MCP-12, MCP-13, MCP-16, plus AI SAFE² memory-governance controls.
A tool parameter, redirect, or server-driven resource request can attempt to reach loopback, link-local, metadata, private-network, or file resources that should not be reachable from an untrusted integration.
Relevant control: MCP-19.
mcp-safe-wrapConsumer-side wrapping can provide protections independent of the remote server’s implementation, including:
A wrapper reduces exposure but does not prove that the remote server satisfies all profile controls.
mcp-scoremcp-score can help assess observable server posture before connection. A black-box score is a risk signal, not a complete conformance certification, because many requirements depend on internal authorization, provenance, and evidence behavior that cannot be proven externally.
mcp-scanStatic scanning can detect high-value implementation patterns in code that is available for inspection. It cannot establish runtime audience binding, complete mediation, or evidence integrity on its own.
Mcp-Session-Id only as a principal-scoped compatibility state handle.The consumer protections map across the current 19-control profile rather than the historical 13-control baseline.
Representative mappings:
| Consumer protection | Profile controls |
|---|---|
| Returned-content scanning | MCP-2 |
| Local/server integrity checks | MCP-4 |
| Consumer-controlled audit | MCP-5 |
| Cost ceilings | MCP-8 |
| Secret redaction/brokering | MCP-9 |
| Catalog/schema pinning | MCP-11, MCP-18 |
| State-handle discipline | MCP-12, MCP-16 |
| Extension restrictions | MCP-14 |
| Replay/request binding | MCP-17 |
| Resource/audience/SSRF validation | MCP-19 |
Normative profile: CP.5.MCP v3.1
The original April 2026 consumer-risk findings remain historical evidence for the need for client-side protection. v3.1 extends that model to the current protocol profile and removes session dependence from the governance claim.
Research Note 023 provides the companion server/profile architecture rationale.
| Framework Home | Research 023 | CP.5.MCP | MCP Toolkit | Scanner |
AI SAFE² v3.1 Research Foundation · Cyber Strategy Institute
| Previous research note | Research Index |
| Framework Home | Cross-Pillar Governance | NEXUS | Challenge Lab |
AI SAFE² v3.1 | Cyber Strategy Institute