MCP resumed state changes authorization or request meaning
An MRTR server trusts modified or context-mismatched requestState when it affects a protected resumed operation.
Candidate CWE: CWE-345 · CWE-863
Test hypothesis#
In a version-matched local fixture, compare untouched state with a single alteration, cross-principal state and changed originating arguments. Exercise a harmless protected operation.
Evidence required#
Preserve protocol/version, state digest, issuer and presenting principals, original/resumed argument digests, validation result and unauthorized stub effect.
Rule out false positives#
A parser failure, state that affects only request failure, or an implementation using another protocol era is not this finding. Do not assume client instructions to keep state opaque constrain a hostile client.
Playbook and command references#
- AI state: memory, resumed work, retries and private caches — Test persistent context, task ownership, MCP request-state integrity, duplicate effects and caches across identities and time.
- AI tools: input trust, execution identity and approvals — Prove when lower-trust content changes a protected tool action, then locate the missing authorization or consent boundary.
Find the associated command snippets
Referenced by these target playbooks#
Report checklist#
- Capture the affected version, configuration, identities, and object ownership.
- Preserve a valid baseline and a negative control.
- Reproduce the forbidden data access, action, or state change on controlled fixtures.
- Explain the intended security rule and why the observed behavior violates it.
- State prerequisites, uncertainty, cleanup, and the smallest demonstrated impact.
Conditional ATT&CK mapping#
No direct ATT&CK mapping selected. Record the weakness and demonstrated impact without forcing an adversary-behavior classification. See the mapping guide.