# web3_revoke_key

Revoke a specific API key. Requires a fresh SIWE challenge signed with personal_sign.

Agent View of the PolicyLayer registry record for `web3_revoke_key`. HTML page: https://policylayer.com/tools/0xarchiveio-0xarchive-mcp/web3-revoke-key

## Facts

- Tool: `web3_revoke_key`
- Server: 0xarchive (`0xarchiveio/0xarchive-mcp`) — https://policylayer.com/tools/0xarchiveio-0xarchive-mcp.md
- Homepage: https://github.com/0xArchiveIO/0xarchive-mcp
- Risk category: Destructive (Critical risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Hidden

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

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "web3_revoke_key",
    "arguments": {}
  }
}
```

## Why web3_revoke_key is rated Critical

Revoking an API key is an irreversible action that permanently destroys access credentials. Once revoked, the key cannot be restored, making this a destructive operation. Misuse by an AI agent could lock out legitimate users or services from the platform, with high blast radius if the wrong key is revoked.

From the tool's own definition: "Revoke a specific API key"

## Use case

AI agents call web3_revoke_key to permanently remove resources in 0xarchive, 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 0xarchive:

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

## Other tools on 0xarchive (4)

- `web3_subscribe` — Financial — https://policylayer.com/tools/0xarchiveio-0xarchive-mcp/web3-subscribe.md
- `web3_challenge` — Read — https://policylayer.com/tools/0xarchiveio-0xarchive-mcp/web3-challenge.md
- `web3_list_keys` — Read — https://policylayer.com/tools/0xarchiveio-0xarchive-mcp/web3-list-keys.md
- `web3_signup` — Write — https://policylayer.com/tools/0xarchiveio-0xarchive-mcp/web3-signup.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=0xarchiveio-0xarchive-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/0xarchiveio-0xarchive-mcp