Request a new challenge string from the tether.name API. This challenge must be signed and submitted back for verification.
AI agents call request_challenge to retrieve information from Tether Name without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple query to obtain a challenge value for cryptographic verification purposes. While it initiates part of an authentication flow, the act of requesting a challenge is non-destructive and read-only. The actual verification happens when the signed challenge is submitted via 'submit_proof'.
From the tool's definition The tool 'request_challenge' retrieves a challenge string from the API with no side effects. The description states it 'request[s] a new challenge string' which is a read operation—it obtains data without modifying, deleting, or executing arbitrary operations.
Attacks that exploit this kind of access
Request a new challenge string from the tether.name API. This challenge must be signed and submitted back for verification. It is categorised as a Read tool in the Tether Name MCP Server, which means it retrieves data without modifying state.
Register the Tether Name MCP server in PolicyLayer and add a rule for request_challenge: 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.
request_challenge 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 request_challenge 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_challenge. 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_challenge 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 →