Perform complete identity verification in one call. Requests a challenge, signs it with the configured private key, and submits the proof to tether.name for verification.
AI agents invoke verify_identity to trigger actions in Tether Name. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool performs a multi-step external operation: it requests a challenge from a remote service, signs it using a private key, and submits the signed proof to an external server. This constitutes triggering external operations with side effects (authentication/verification state change on tether.name), placing it in the Execute category.
From the tool's definition Requests a challenge, signs it with the configured private key, and submits the proof to tether.name for verification
Attacks that exploit this kind of access
Perform complete identity verification in one call. Requests a challenge, signs it with the configured private key, and submits the proof to tether.name for verification. It is categorised as a Execute tool in the Tether Name MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Tether Name MCP server in PolicyLayer and add a rule for verify_identity: 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 Tether Name. Nothing to install.
verify_identity is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the verify_identity 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 verify_identity. 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.
verify_identity is provided by the Tether Name MCP server (tether-name-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 →