Revoke an agent key. Requires TETHER_API_KEY plus step-up verification via stepUpCode or challenge+proof.
AI agents call revoke_agent_key to permanently remove resources in Tether Name — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Key revocation is an irreversible action that destroys the ability of an agent to authenticate using that specific credential. While not data deletion in the traditional sense, it permanently disables a security credential, making it impossible to restore without creating a new key. This fits the Destructive category (actions that cannot be undone).
From the tool's definition Tool name 'revoke_agent_key' combined with description stating it 'Revoke[s] an agent key' indicates irreversible removal/disabling of cryptographic credentials.
Attacks that exploit this kind of access
Revoke an agent key. Requires TETHER_API_KEY plus step-up verification via stepUpCode or challenge+proof. It is categorised as a Destructive tool in the Tether Name MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tether Name MCP server in PolicyLayer and add a rule for revoke_agent_key: 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.
revoke_agent_key is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the revoke_agent_key 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 revoke_agent_key. 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.
revoke_agent_key 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 →