How to meet it
OWASP AISVS v1.01
Model Context Protocol (MCP) Security · Schema, Message, and Input Validation
Bind consent to the approved MCP endpoint
Verify that MCP clients bind each approved MCP server's granted consent and authorization to the connection endpoint approved for that server, and require user re-approval before any further interaction once that endpoint changes.
OWASP AISVS v1.01, requirement 10.4.10
In plain English
Tie each approval to the server address it was given for. If the address changes, ask the user again before doing anything else.
What good looks like
- Consent is stored with the approved endpoint.
- Endpoint changes trigger re-approval.
- No calls are made until re-approved.
How teams usually do it
- Storing the endpoint with the grant and comparing on connect.
Evidence an auditor would accept
- Tests changing the endpoint.
Common mistakes
- Following redirects to a new endpoint with the old approval.
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.