Low Risk

getNetworks

REQUIRED FIRST STEP: Get all supported blockchain networks. Always call this first to see available networks before using any network-specific functions. Returns network IDs like

How to control getNetworks ↓

What getNetworks does on Sperax Ecosystem Crypto & DeFI MCP Server

AI agents call getNetworks to retrieve information from Sperax Ecosystem Crypto & DeFI 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 getNetworks needs a policy

The tool queries and returns static configuration data about available blockchain networks. It performs no modifications, executions, deletions, or financial operations. It is a foundational lookup operation that agents use to discover available options before performing other actions. This is a classic Read operation with minimal risk—the only potential misuse would be information gathering, which is low severity.

From the tool's definition Tool name 'getNetworks' and description indicate it 'Get[s] all supported blockchain networks' and 'Returns network IDs'. This is a pure data retrieval operation with no side effects.

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

How to control getNetworks

PolicyLayer is an MCP gateway — it sits between your AI agents and Sperax Ecosystem Crypto & DeFI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for getNetworks:

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

getNetworks 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 Sperax Ecosystem Crypto & DeFI 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 getNetworks

What does the getNetworks tool do? +

REQUIRED FIRST STEP: Get all supported blockchain networks. Always call this first to see available networks before using any network-specific functions. Returns network IDs like. It is categorised as a Read tool in the Sperax Ecosystem Crypto & DeFI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on getNetworks? +

Register the Sperax Ecosystem Crypto & DeFI MCP Server MCP server in PolicyLayer and add a rule for getNetworks: 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 Sperax Ecosystem Crypto & DeFI MCP Server. Nothing to install.

What risk level is getNetworks? +

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

Can I rate-limit getNetworks? +

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

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

getNetworks is provided by the Sperax Ecosystem Crypto & DeFI MCP Server MCP server (sperax/sperax-crypto-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sperax Ecosystem Crypto & DeFI MCP Server tool call.

Start from Sperax Ecosystem Crypto & DeFI 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.

1318 Sperax Ecosystem Crypto & DeFI 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.