Returns true if client is actively listening for network connections
AI agents call net_listening 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 queries the state of the EVM client's network listener status and returns a simple boolean response. It is a read-only operation that retrieves information about the node without modifying any data, executing code, or triggering external operations. The blast radius of misuse is minimal—an attacker gaining this information cannot perform harmful actions with it.
From the tool's definition Tool name 'net_listening' and description 'Returns true if client is actively listening for network connections' — a boolean query about node status with no side effects.
Attacks that exploit this kind of access
Returns true if client is actively listening for network connections. 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 net_listening: 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.
net_listening 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 net_listening 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 net_listening. 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.
net_listening 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 →