New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

util_evm_chain_match_check

EVM Chain Match Check compares transaction and expected chain identifiers from bounded caller-supplied values without an external provider. Call EVM Chain Match Check before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized t...

SERVERDelx Mcp A2a SOURCEhttps://api.delx.ai/v1/mcp
Low RISK CLASS
Category Read
Parameters 22 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-davidmosiah-delx-mcp-a2a/util-evm-chain-match-check.md

What util_evm_chain_match_check does on Delx Mcp A2a

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

ParameterTypeRequiredDescription
expected_chain_id integer Yes Expected Chain Id supplied to EVM Chain Match Check; used only for this bounded calculation and processed in memory without retention.
transaction_chain_id integer Yes Transaction Chain Id supplied to EVM Chain Match Check; used only for this bounded calculation and processed in memory without retention.

Parameters from the server's own tool schema.

Why util_evm_chain_match_check is rated Low

Even though util_evm_chain_match_check only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about util_evm_chain_match_check

What does the util_evm_chain_match_check tool do? +

EVM Chain Match Check compares transaction and expected chain identifiers from bounded caller-supplied values without an external provider. Call EVM Chain Match Check before signing, submitting, replacing, or accepting an EVM/Base transaction assembled from caller-owned data. Returns normalized transaction evidence, calculated budget or shape findings, and a fail-closed preflight status for EVM Chain Match Check as versioned deterministic JSON. Limitation: Uses caller-supplied values only; it performs no RPC call, signing, broadcasting, balance lookup, custody, trading, or live-chain claim. It is categorised as a Read tool in the Delx Mcp A2a MCP Server, which means it retrieves data without modifying state.

What parameters does util_evm_chain_match_check accept? +

util_evm_chain_match_check accepts 2 parameters: expected_chain_id, transaction_chain_id. Required: expected_chain_id, transaction_chain_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on util_evm_chain_match_check? +

Register the Delx Mcp A2a MCP server in PolicyLayer and add a rule for util_evm_chain_match_check: 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.

What risk level is util_evm_chain_match_check? +

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

Can I rate-limit util_evm_chain_match_check? +

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

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

util_evm_chain_match_check 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Delx Mcp A2a's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.