AI agents call twilio_check_verify to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | |
code | string | Yes | The OTP code entered by the user |
auth_token | string | Yes | |
account_sid | string | Yes | |
service_sid | string | Yes |
Parameters from the server's own tool schema.
The tool performs a verification check—it validates whether a user-submitted code matches an expected value. This is a read operation that queries state without creating, modifying, deleting, or executing external commands. The severity is low because misuse would only affect authentication logic, not data integrity or external operations, and the blast radius is limited to credential validation.
From the tool's definition Tool name 'twilio_check_verify' and description 'Check a verification code submitted by a user via Twilio Verify' indicate a query/validation operation that retrieves or checks status without modifying data.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
Check a verification code submitted by a user via Twilio Verify. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
twilio_check_verify accepts 5 parameters: to, code, auth_token, account_sid, service_sid. Required: to, code, auth_token, account_sid, service_sid. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for twilio_check_verify: 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 UnClick. Nothing to install.
twilio_check_verify is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the twilio_check_verify 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 twilio_check_verify. 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.
twilio_check_verify is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →