Low Risk

get_supported_networks

Get a list of all supported EVM networks

How to control get_supported_networks ↓

What get_supported_networks does on EVM MCP Server

AI agents call get_supported_networks 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.

Low Risk

Why get_supported_networks needs a policy

This tool retrieves static or configuration metadata about supported networks. It performs no state changes, does not execute code or transactions, and has no financial implications. It is purely informational, making it a Read operation with low blast radius if misused by an AI agent.

From the tool's definition Tool name 'get_supported_networks' and description 'Get a list of all supported EVM networks' indicate a query operation that retrieves configuration data with no side effects.

Documented attack patterns abuse exactly the kind of access get_supported_networks gives an agent:

How to control get_supported_networks

PolicyLayer is an MCP gateway — it sits between your AI agents and EVM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_supported_networks:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_supported_networks": {}
  }
}

get_supported_networks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register EVM MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_supported_networks

What does the get_supported_networks tool do? +

Get a list of all supported EVM networks. It is categorised as a Read tool in the EVM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_supported_networks? +

Register the EVM MCP Server MCP server in PolicyLayer and add a rule for get_supported_networks: 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.

What risk level is get_supported_networks? +

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

Can I rate-limit get_supported_networks? +

Yes. Add a rate_limit block to the get_supported_networks 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 get_supported_networks completely? +

Set action: deny in the PolicyLayer policy for get_supported_networks. 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 get_supported_networks? +

get_supported_networks is provided by the EVM MCP Server MCP server (mcpdotdirect/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every EVM MCP Server tool call.

Start from EVM MCP Server, 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.

25 EVM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.