How to meet it
OWASP AISVS v1.01
Model Context Protocol (MCP) Security · Schema, Message, and Input Validation
Don't collect secrets through elicitation
Verify that MCP servers do not use form-mode elicitation to request secrets or payment credentials, and that in URL-mode elicitation the user completing the flow is the same user who initiated it.
OWASP AISVS v1.01, requirement 10.4.18
In plain English
Do not ask for secrets or payment details through form-style elicitation. In URL-style flows, make sure the person finishing the flow is the person who started it.
What good looks like
- Forms never request secrets or payment credentials.
- URL flows check the completing user matches the initiating user.
- Tests cover a mismatched user.
How teams usually do it
- Binding the URL flow to a session and checking it on completion.
Evidence an auditor would accept
- Flow design and tests.
Common mistakes
- Asking for an API key in a form field.
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.