How to meet it
OWASP AISVS v1.01
Model Context Protocol (MCP) Security · Authentication & Authorization
Protect request state from tampering
Verify that MCP servers protect the integrity of `requestState` that influences authorization, resource access, or business logic, and reject state that fails verification.
OWASP AISVS v1.01, requirement 10.2.8
In plain English
If a server sends request state that affects authorisation or business logic, protect it so a client cannot change it, and reject state that fails the check.
What good looks like
- Such state is signed or encrypted by the server.
- State is verified on return.
- Tampered state is rejected.
How teams usually do it
- Signing request state with a server key, or storing it server side and sending only a reference.
Evidence an auditor would accept
- Code and tests with altered state.
Common mistakes
- Trusting state the client sends back unchanged.
Not sure which requirements apply to your system? Take the assessment.
Requirement text from the OWASP AI Security Verification Standard, licensed under CC BY-SA 4.0. This guidance is shared under the same licence.