# revoke_api_key

Revoke an API key by ID. The key stops working immediately.

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

## Facts

- Tool: `revoke_api_key`
- Server: AI Cortex Storage (`https://memory.aic0rt3x.dev/mcp`) — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp.md
- Homepage: https://github.com/https://memory.aic0rt3x.dev/mcp
- 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 |
| --- | --- | --- | --- |
| `key_id` | string | yes | The key ID to revoke, as returned by list_api_keys. |

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": {
      "key_id": "<key_id>"
    }
  }
}
```

## Why revoke_api_key is rated Critical

Revoking an API key is an irreversible action: once revoked, the key cannot be re-enabled. Any agent or service relying on that key will immediately lose access. This matches the Destructive category (irreversible deletion/invalidation). The blast radius is high because misuse could lock out legitimate users or dependent AI agents from the storage service.

From the tool's own definition: "'Revoke an API key by ID. The key stops working immediately.' — revocation is irreversible and takes effect instantly."

## Use case

AI agents call revoke_api_key to permanently remove resources in AI Cortex Storage, 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 AI Cortex Storage:

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

## Other tools on AI Cortex Storage (14)

- `delete_memory` — Destructive — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/delete-memory.md
- `settle_balance` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/settle-balance.md
- `submit_feature_request` — Financial — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-feature-request.md
- `get_account` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-account.md
- `get_memory` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/get-memory.md
- `list_api_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-api-keys.md
- `list_keys` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-keys.md
- `list_namespaces` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-namespaces.md
- `list_payments` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/list-payments.md
- `search_by_tag` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/search-by-tag.md
- `top_memories` — Read — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/top-memories.md
- `create_api_key` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/create-api-key.md
- `put_memory` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/put-memory.md
- `submit_exit_feedback` — Write — https://policylayer.com/tools/dev-aic0rt3x-memory-mcp/submit-exit-feedback.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-aic0rt3x-memory-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-aic0rt3x-memory-mcp