rotate_api_key
Mint a linked successor for an existing key. Returns the successor plaintext exactly once — store it now. The predecessor stays valid through its overlap window so callers can swap without downtime. Owner anywhere, editor on own keys.
This record as markdown: /tools/dev-echorelay-management/rotate-api-key.md
What rotate_api_key does on EchoRelay
AI agents use rotate_api_key to create or update resources in EchoRelay, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your EchoRelay environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
keyId | string | Yes | UUID of the key to rotate. |
Parameters from the server's own tool schema.
Why rotate_api_key is rated Medium
Rotating an API key creates a new credential (Write), but the security implications are high: the new key plaintext is returned once and must be stored, while the old key remains valid during an overlap window. Misuse could expose new credentials or disrupt authentication flows.
From the tool's definition Mint a linked successor for an existing key. Returns the successor plaintext exactly once — store it now. The predecessor stays valid through its overlap window so callers can swap without downtime.
Attacks that exploit this kind of access
The rule that runs rotate_api_key safely
PolicyLayer is an MCP gateway: it sits between your AI agents and EchoRelay, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For rotate_api_key, this is the rule to start with:
rotate_api_key stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every rotate_api_key call is checked against it from then on.
Questions about rotate_api_key
Mint a linked successor for an existing key. Returns the successor plaintext exactly once — store it now. The predecessor stays valid through its overlap window so callers can swap without downtime. Owner anywhere, editor on own keys. It is categorised as a Write tool in the EchoRelay MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
rotate_api_key accepts 1 parameter: keyId. Required: keyId. The full parameter table on this page comes from the server's own tool schema.
Register the EchoRelay MCP server in PolicyLayer and add a rule for rotate_api_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 EchoRelay. Nothing to install.
rotate_api_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_api_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_api_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_api_key is provided by the EchoRelay MCP server (https://mcp.echorelay.dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on EchoRelay, and thousands of servers like it.
This server
Across the catalogue