Skip to main content
Glama

Ingravity Autonomous EVM Security & DeFi Guard (x402 v2)

EVM Transaction Firewall

ingravity_inspectEvmTransactionFirewall
Read-onlyIdempotent

Simulates pre-sign EVM calldata (to, data, optional from and wei value defaulting to '0') across five chains (chainId default 8453 Base) to block drainers before wallet signing. Strictly read-only: decodes ERC-20 approve, NFT setApprovalForAll, EIP-2612/Permit2 signatures, and recursive multicall while reading live RPC bytecode and EIP-1967/1167 slots to return SAFE/WARNING/BLOCK_DRAINER (PROCEED/CAUTION/ABORT) and unsigned revocation calldata. Costs $0.10 USDC on Base via x402 v2 (unpaid returns isError: true); active critical compromises require 0.15% SLA or 5%-10% Safe-Harbor bounty settlement to unmask spender coordinates. Call before signing transactions; use ingravity_scanTokenRugpullAndHoneypot for token due diligence without calldata.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>"
    },
    "name": "ingravity_inspectEvmTransactionFirewall"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesTarget EVM contract, token, or recipient 42-character hex address (0x...).
dataNoHexadecimal transaction calldata (0x...); pass '0x' for a plain native ETH transfer.
fromNoOptional sender wallet address (0x...) also matched against active ZK-EC whale exposure dossiers.
valueNoOptional native ETH value in wei as a decimal string.0
chainIdNoTarget EVM chain ID for live RPC bytecode/EIP-1967 inspection (8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum; unknown falls back to 8453).
ticketIdNoOptional ZK-EC blinded exposure ticket ID (TICKET-8453-...) to unseal full remediation coordinates upon x402 rescue settlement.
capitalAtRiskUsdNoOptional protected capital value in USD for +0.15% Pre-Flight SLA / Safe-Harbor rescue quoting.

Output Schema

NameRequiredDescriptionDefault
actionYesPre-sign action recommendation.
signalYesTraffic-light risk signal.
chainIdYesResolved EVM chain ID used for live RPC inspection.
settledYesWhether x402 USDC payment settled cleanly.
verdictYesDetailed firewall classification.
decisionYesNormalized risk decision.
selectorYes4-byte function selector ('0x' for empty calldata, 'INVALID' if malformed hex).
triggersYesTriggered drainer/permission heuristics and RPC checks.
riskScoreYesCumulative risk score from 0 to 100.
decodedActionYesHuman-readable decoded calldata action.
decodedParamsNoDecoded ABI arguments (e.g., spender, operator, owner, value, deadline).
agentDirectiveYesExecution directive explaining how to proceed or revoke.
liveOnChainForensicsNoLive 5-EVM RPC bytecode and EIP-1967 proxy slot inspection (null when unavailable or malformed).
executableRemediationTxNoUnsigned EIP-5792 wallet_sendCalls and approve(spender, 0) calldata when spender is decoded (or lock notice when masked in pre-flight tier).
savedCapitalEstimateUsdYesEstimated wallet value protected if drainer blocked.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial context beyond the annotations: decoding coverage (ERC-20 approve, setApprovalForAll, EIP-2612/Permit2, recursive multicall), live RPC bytecode and EIP-1967/1167 slot reads, the SAFE/WARNING/BLOCK_DRAINER output classes, and unsigned revocation calldata. It also discloses cost ($0.10 USDC via x402 v2, unpaid returns isError: true) and escalation terms (0.15% SLA / 5%-10% Safe-Harbor bounty). Only a minor gap remains around what the SLA/bounty jargon concretely entails for the caller.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose and read-only stance are front-loaded, but the single dense paragraph packs heavy jargon (ZK-EC, x402 v2, EIP-1967/1167, Safe-Harbor) into run-on clauses. It is information-rich but harder to scan than a well-structured definition with clear sectioning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given annotations, a 100% schema, and a present output schema, the description covers what is needed: purpose, read-only guarantee, cost and payment failure mode, return categories, and the sibling alternative. Nothing critical for correct invocation appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so both the defaults (wei value '0', chainId 8453) and the chain enum are already documented in the schema. The description restates these rather than adding format or edge-case meaning, so it meets the baseline without exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Simulates pre-sign EVM calldata') plus the risk it addresses ('block drainers before wallet signing'), and explicitly names the sibling it is not (ingravity_scanTokenRugpullAndHoneypot for token due diligence without calldata). An agent can distinguish it from siblings without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit trigger ('Call before signing transactions') and names the alternative plus the condition that selects it ('use ingravity_scanTokenRugpullAndHoneypot for token due diligence without calldata'). The when-to-use boundary is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.