Lists configured wallet aliases and known token/contract addresses
AI agents call list_known_addresses to retrieve information from EVM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays pre-configured metadata (aliases and known addresses) without side effects. It performs a simple lookup/list operation analogous to reading configuration or a database view. No blockchain state is modified, no transactions are executed, and no irreversible actions occur.
From the tool's definition Tool name 'list_known_addresses' combined with description 'Lists configured wallet aliases and known token/contract addresses' indicates a purely informational retrieval operation with no data modification, deletion, or execution capability.
Attacks that exploit this kind of access
Lists configured wallet aliases and known token/contract addresses. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the EVM MCP Server MCP server in PolicyLayer and add a rule for list_known_addresses: 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 EVM MCP Server. Nothing to install.
list_known_addresses 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 list_known_addresses 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 list_known_addresses. 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.
list_known_addresses is provided by the EVM MCP Server MCP server (jamesanz/evm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →