revoke_api_key
Manual hard revoke. The key stops authenticating on the next request. Owner anywhere, editor on own keys.
This record as markdown: /tools/dev-echorelay-management/revoke-api-key.md
What revoke_api_key does on EchoRelay
AI agents call revoke_api_key to permanently remove resources in EchoRelay, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
keyId | string | Yes | UUID of the key to revoke. |
Parameters from the server's own tool schema.
Why revoke_api_key is rated Critical
Revoking an API key is an irreversible destructive action — once revoked, the key permanently loses authentication capability. This cannot be undone (a new key would need to be issued), and misuse could immediately break integrations or lock out legitimate users/services that depend on that key.
From the tool's definition Manual hard revoke. The key stops authenticating on the next request.
Attacks that exploit this kind of access
The rule that runs revoke_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 revoke_api_key, this is the rule to start with:
revoke_api_key is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect EchoRelay, apply this rule, and every revoke_api_key call is checked against it from then on.
Questions about revoke_api_key
Manual hard revoke. The key stops authenticating on the next request. Owner anywhere, editor on own keys. It is categorised as a Destructive tool in the EchoRelay MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
revoke_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 revoke_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.
revoke_api_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_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 revoke_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.
revoke_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.
Across the catalogue