# revoke_api_key

Manual hard revoke. The key stops authenticating on the next request. Owner anywhere, editor on own keys.

Agent View of the PolicyLayer registry record for `revoke_api_key`. HTML page: https://policylayer.com/tools/dev-echorelay-management/revoke-api-key

## Facts

- Tool: `revoke_api_key`
- Server: EchoRelay (`https://mcp.echorelay.dev`) — https://policylayer.com/tools/dev-echorelay-management.md
- Homepage: https://github.com/https://mcp.echorelay.dev
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Hidden

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `keyId` | string | yes | UUID of the key to revoke. |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "revoke_api_key",
    "arguments": {
      "keyId": "<keyId>"
    }
  }
}
```

## 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 own definition: "Manual hard revoke. The key stops authenticating on the next request."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Hidden**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches EchoRelay:

```json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "revoke_api_key"
  ]
}
```

## Other tools on EchoRelay (77)

- `cancel_line_publish` — Destructive — https://policylayer.com/tools/dev-echorelay-management/cancel-line-publish.md
- `delete_credential` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-credential.md
- `delete_endpoint` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-endpoint.md
- `delete_line` — Destructive — https://policylayer.com/tools/dev-echorelay-management/delete-line.md
- `discard_dlq_entry` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-dlq-entry.md
- `discard_draft_endpoint` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-draft-endpoint.md
- `discard_line_draft` — Destructive — https://policylayer.com/tools/dev-echorelay-management/discard-line-draft.md
- `remove_member` — Destructive — https://policylayer.com/tools/dev-echorelay-management/remove-member.md
- `revoke_project_token` — Destructive — https://policylayer.com/tools/dev-echorelay-management/revoke-project-token.md
- `rollback_config` — Destructive — https://policylayer.com/tools/dev-echorelay-management/rollback-config.md
- `dry_run_endpoint` — Execute — https://policylayer.com/tools/dev-echorelay-management/dry-run-endpoint.md
- `duplicate_line` — Execute — https://policylayer.com/tools/dev-echorelay-management/duplicate-line.md
- `cancel_subscription` — Financial — https://policylayer.com/tools/dev-echorelay-management/cancel-subscription.md
- `change_plan` — Financial — https://policylayer.com/tools/dev-echorelay-management/change-plan.md
- `downgrade_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/downgrade-addon.md
- `retry_dlq_entry` — Financial — https://policylayer.com/tools/dev-echorelay-management/retry-dlq-entry.md
- `start_subscription` — Financial — https://policylayer.com/tools/dev-echorelay-management/start-subscription.md
- `start_topup` — Financial — https://policylayer.com/tools/dev-echorelay-management/start-topup.md
- `subscribe_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/subscribe-addon.md
- `unsubscribe_addon` — Financial — https://policylayer.com/tools/dev-echorelay-management/unsubscribe-addon.md
- `default_endpoint_template` — Read — https://policylayer.com/tools/dev-echorelay-management/default-endpoint-template.md
- `get_billing` — Read — https://policylayer.com/tools/dev-echorelay-management/get-billing.md
- `get_config` — Read — https://policylayer.com/tools/dev-echorelay-management/get-config.md
- `get_dlq_entry` — Read — https://policylayer.com/tools/dev-echorelay-management/get-dlq-entry.md
- `get_endpoint` — Read — https://policylayer.com/tools/dev-echorelay-management/get-endpoint.md
- `get_key_policy` — Read — https://policylayer.com/tools/dev-echorelay-management/get-key-policy.md
- `get_line_draft` — Read — https://policylayer.com/tools/dev-echorelay-management/get-line-draft.md
- `get_metrics` — Read — https://policylayer.com/tools/dev-echorelay-management/get-metrics.md
- `get_project` — Read — https://policylayer.com/tools/dev-echorelay-management/get-project.md
- `get_receipts` — Read — https://policylayer.com/tools/dev-echorelay-management/get-receipts.md
- …and 47 more: https://policylayer.com/tools/dev-echorelay-management.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-echorelay-management · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-echorelay-management