Revoke a specific API key. Requires a fresh SIWE challenge signed with personal_sign.
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.
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 definition Revoke a specific API key
Documented attack patterns abuse exactly the kind of access web3_revoke_key gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and 0xarchive, and nothing reaches the server without passing your rules. This is the rule we recommend for web3_revoke_key:
{
"version": "1",
"default": "deny",
"hide": [
"web3_revoke_key"
]
}web3_revoke_key disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Revoke a specific API key. Requires a fresh SIWE challenge signed with personal_sign. It is categorised as a Destructive tool in the 0xarchive MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the 0xarchive MCP server in PolicyLayer and add a rule for web3_revoke_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 0xarchive. Nothing to install.
web3_revoke_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 web3_revoke_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 web3_revoke_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.
web3_revoke_key is provided by the 0xarchive MCP server (0xarchiveio/0xarchive-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from 0xarchive, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
5 0xarchive tools catalogued and risk-classified — across an index of 43,000+ MCP servers.