Request Meta to send a verification code to the configured phone number via SMS or voice. Use before verify_code.
AI agents use request_verification_code to create or update resources in Mcp Ap2 — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Ap2 environment.
This tool initiates outbound communication and creates a verification token, which constitutes a write operation. While not destructive or financial, it performs a stateful action with external side effects. Severity is medium because abuse could result in SMS/voice spam or account compromise attempts, though the impact is limited compared to financial or destructive operations.
From the tool's definition Tool 'request_verification_code' triggers an action that sends a verification code via SMS or voice to a configured phone number. This is a side effect that modifies external state (sends communication) and is reversible in nature.
Documented attack patterns abuse exactly the kind of access request_verification_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Ap2, and nothing reaches the server without passing your rules. This is the rule we recommend for request_verification_code:
{
"version": "1",
"default": "deny",
"tools": {
"request_verification_code": {
"limits": [
{
"counter": "request_verification_code_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}request_verification_code stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Request Meta to send a verification code to the configured phone number via SMS or voice. Use before verify_code. It is categorised as a Write tool in the Mcp Ap2 MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Ap2 MCP server in PolicyLayer and add a rule for request_verification_code: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Mcp Ap2. Nothing to install.
request_verification_code is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the request_verification_code rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for request_verification_code. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
request_verification_code is provided by the Mcp Ap2 MCP server (@codespar/mcp-ap2). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Ap2, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
1300 Mcp Ap2 tools catalogued and risk-classified — across an index of 43,000+ MCP servers.