Rotate an agent key. Requires TETHER_API_KEY plus step-up verification via stepUpCode or challenge+proof.
AI agents use rotate_agent_key to create or update resources in Tether Name — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tether Name environment.
Rotating an agent key modifies the agent's authentication credentials by replacing the existing key with a new one. This is a Write operation (reversible in the sense that a new key is generated, though the old key is invalidated). The severity is high because misuse could lock out legitimate agents or grant unauthorized access by replacing valid keys, impacting identity and access management across the system.
From the tool's definition Rotate an agent key. Requires TETHER_API_KEY plus step-up verification via stepUpCode or challenge+proof.
Attacks that exploit this kind of access
Rotate an agent key. Requires TETHER_API_KEY plus step-up verification via stepUpCode or challenge+proof. It is categorised as a Write tool in the Tether Name MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tether Name MCP server in PolicyLayer and add a rule for rotate_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.
rotate_agent_key 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 rotate_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 rotate_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.
rotate_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 →