List all API keys for a wallet. Requires a fresh SIWE challenge signed with personal_sign.
AI agents call web3_list_keys to retrieve information from 0xarchive without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and enumerates API keys associated with a wallet. While the action itself is read-only (no data is modified or deleted), the sensitivity of the data returned—authentication credentials—elevates the severity. Unauthorized listing of API keys could enable an attacker to impersonate the wallet owner and access crypto market data or execute trades.
From the tool's definition Tool description states it 'List[s] all API keys for a wallet' - a retrieval operation with no modification capability.
Documented attack patterns abuse exactly the kind of access web3_list_keys 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_list_keys:
{
"version": "1",
"default": "deny",
"tools": {
"web3_list_keys": {}
}
}web3_list_keys is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all API keys for a wallet. Requires a fresh SIWE challenge signed with personal_sign. It is categorised as a Read tool in the 0xarchive MCP Server, which means it retrieves data without modifying state.
Register the 0xarchive MCP server in PolicyLayer and add a rule for web3_list_keys: 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_list_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the web3_list_keys 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_list_keys. 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_list_keys 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.