Get the local wallet evm address.
AI agents call local_wallet_address to retrieve information from Web3 Assistant MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to retrieve wallet address information. It has no side effects, does not modify data, does not execute code or transactions, and does not involve financial operations.
From the tool's definition Tool name 'local_wallet_address' and description 'Get the local wallet evm address' indicate a retrieval operation that queries the address of a locally managed wallet without modifying state or executing transactions.
Attacks that exploit this kind of access
Get the local wallet evm address. It is categorised as a Read tool in the Web3 Assistant MCP MCP Server, which means it retrieves data without modifying state.
Register the Web3 Assistant MCP server in PolicyLayer and add a rule for local_wallet_address: 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 Web3 Assistant MCP. Nothing to install.
local_wallet_address 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 local_wallet_address 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 local_wallet_address. 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.
local_wallet_address is provided by the Web3 Assistant MCP server (laplaceman/web3-assistant-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 →