web3_list_keys

List all API keys for a wallet. Requires a fresh SIWE challenge signed with personal_sign.

SERVER0xarchive SOURCE0xarchiveio/0xarchive-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/0xarchiveio-0xarchive-mcp/web3-list-keys.md

WHAT IT DOES

What web3_list_keys does on 0xarchive

AI agents call web3_list_keys to retrieve information from 0xarchive without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why web3_list_keys is rated Low

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.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs web3_list_keys safely

PolicyLayer is an MCP gateway: it sits between your AI agents and 0xarchive, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For web3_list_keys, this is the rule to start with:

web3_list_keys Allowed

web3_list_keys is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "web3_list_keys": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 0xarchive, apply this rule, and every web3_list_keys call is checked against it from then on.

FAQ

Questions about web3_list_keys

What does the web3_list_keys tool do? +

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.

How do I enforce a policy on web3_list_keys? +

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.

What risk level is web3_list_keys? +

web3_list_keys is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit web3_list_keys? +

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.

How do I block web3_list_keys completely? +

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.

What MCP server provides web3_list_keys? +

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.

KEEP EXPLORING

More on 0xarchive, and thousands of servers like it.

This server

All 5 0xarchive tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →