get_chain_network_info
Look up static blockchain network metadata and chain IDs for supported EVM and Solana networks. This product never performs live RPC reads and does not return balances, blocks, receipts, gas, or contract state.
This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/get-chain-network-info.md
What get_chain_network_info does on Delx Mcp A2a
AI agents call get_chain_network_info to retrieve information from Delx Mcp A2a without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
network | string | — | Optional network name or alias such as base, ethereum, polygon, arbitrum-one, optimism, or solana. |
chain_id | integer | — | Optional EVM decimal chain ID. Omit network and chain_id to return the full static registry. |
Parameters from the server's own tool schema.
Why get_chain_network_info is rated Low
The tool retrieves static metadata about blockchain networks without any capability to modify data, execute transactions, or trigger external operations. It is a simple lookup function with no destructive, financial, or code execution capabilities. The explicit limitations noted in the description confirm this is a read-only information retrieval operation.
From the tool's definition Tool description explicitly states it 'Look up static blockchain network metadata and chain IDs' and 'never performs live RPC reads' and 'does not return balances, blocks, receipts, gas, or contract state.' This is purely informational retrieval with no side…
Attacks that exploit this kind of access
The rule that runs get_chain_network_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx Mcp A2a, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_chain_network_info, this is the rule to start with:
get_chain_network_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Delx Mcp A2a, apply this rule, and every get_chain_network_info call is checked against it from then on.
Questions about get_chain_network_info
Look up static blockchain network metadata and chain IDs for supported EVM and Solana networks. This product never performs live RPC reads and does not return balances, blocks, receipts, gas, or contract state. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.
get_chain_network_info accepts 2 parameters: network, chain_id. The full parameter table on this page comes from the server's own tool schema.
Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for get_chain_network_info: 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 Delx Mcp A2a. Nothing to install.
get_chain_network_info 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 get_chain_network_info 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 get_chain_network_info. 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.
get_chain_network_info is provided by the Delx Mcp A2a MCP server (https://api.delx.ai/v1/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx Mcp A2a, and thousands of servers like it.
This server
Across the catalogue