reveal_rotation_successor
One-shot retrieval of the plaintext for a successor minted by the auto-rotation scheduler (not by rotate_api_key — that returns its own plaintext directly). Decrypts the at-rest ciphertext, returns it once, then destroys it; a second call errors. Only available while the predecessor still has an ...
This record as markdown: /tools/dev-echorelay-management/reveal-rotation-successor.md
What reveal_rotation_successor does on EchoRelay
AI agents call reveal_rotation_successor to retrieve information from EchoRelay without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
keyId | string | Yes | UUID of the predecessor key whose successor to reveal. |
Parameters from the server's own tool schema.
Why reveal_rotation_successor is rated Low
While the tool does destroy data after use, this is a secondary safeguard mechanism, not the primary purpose. The main function is retrieving (reading) an API key successor in plaintext.
From the tool's definition Tool performs 'One-shot retrieval' and 'returns it once' before destroying the plaintext. The primary action is decryption and retrieval of data ('reveal_rotation_successor').
Attacks that exploit this kind of access
The rule that runs reveal_rotation_successor 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 reveal_rotation_successor, this is the rule to start with:
reveal_rotation_successor is read-only, so it stays allowed. 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 reveal_rotation_successor call is checked against it from then on.
Questions about reveal_rotation_successor
One-shot retrieval of the plaintext for a successor minted by the auto-rotation scheduler (not by rotate_api_key — that returns its own plaintext directly). Decrypts the at-rest ciphertext, returns it once, then destroys it; a second call errors. Only available while the predecessor still has an unrevealed successor. It is categorised as a Read tool in the EchoRelay MCP Server, which means it retrieves data without modifying state.
reveal_rotation_successor 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 reveal_rotation_successor: 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.
reveal_rotation_successor 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 reveal_rotation_successor 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 reveal_rotation_successor. 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.
reveal_rotation_successor 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