How to meet it
OWASP AISVS v1.01
Model Context Protocol (MCP) Security · Schema, Message, and Input Validation
Keep private cached responses private
Verify that MCP clients and intermediaries reuse cached responses marked with a private cache scope only within the authorization context that produced them, and do not cache results of multi round-trip requests.
OWASP AISVS v1.01, requirement 10.4.16
In plain English
Reuse cached responses marked private only for the same authorisation context, and do not cache results of requests that take several round trips.
What good looks like
- Private cache entries are keyed by authorisation context.
- Multi round-trip results are not cached.
- Tests check one user cannot get another's cached result.
How teams usually do it
- Cache keys that include the user or token identity.
Evidence an auditor would accept
- Cache configuration and tests.
Common mistakes
- Caching by tool name and arguments only.
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.