get_supported_networks

Get a list of supported EVM networks

SERVEREVM MCP Server SOURCEchulanpro5/evm-mcp-server

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/chulanpro5-evm-mcp-server/get-supported-networks.md

WHAT IT DOES

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. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_supported_networks is rated Low

This tool performs a simple data retrieval operation—fetching a static list of supported networks. There are no write, execute, destructive, or financial operations involved. It is purely informational and read-only, with minimal blast radius if misused by an AI agent, since the worst outcome would be obtaining network information that is already public.

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

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_supported_networks safely

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

get_supported_networks Allowed

get_supported_networks 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": {
    "get_supported_networks": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect EVM MCP Server, apply this rule, and every get_supported_networks call is checked against it from then on.

FAQ

Questions about get_supported_networks

What does the get_supported_networks tool do? +

Get a list of 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 (chulanpro5/evm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on EVM MCP Server, and thousands of servers like it.

This server

All 36 EVM MCP Server tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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