Skip to main content
Glama

Ingravity Autonomous EVM Security & DeFi Guard (x402 v2)

Flash-Loan Exploit Simulator & Safe-Harbor Planner

ingravity_simulateDeepExploitAndWhitehatBounty
Read-onlyIdempotent

Simulates flash-loan drain vectors, oracle slot0/reserve exposure, and live on-chain TVL across five EVM chains for a target protocol (protocolName required; poolAddress defaults to Base Aerodrome address when omitted, tvlUsd defaults to 250000). Strictly read-only: reads live RPC liquidity and optional Solidity code to compute exploitImmunityScore and unsigned EIP-5792/EOA Safe-Harbor rescue calldata (90%-95% to optional ownerTreasury, 5%-10% whitehat bounty on rescue only) without transferring funds. Set tier to FULL ($45.00 USDC, default) for flashLoanSimulation and rescue bundle or ESSENTIAL ($9.50 USDC) for vulnerabilitySeverity and score; unpaid calls return isError: true and CRITICAL/HIGH PoCs stay sealed under Anti-Bypass. Use for live pool exploitability and rescue planning; use ingravity_generateMultiContractProtocolDossier for multi-file codebase audits.

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": {
      "protocolName": "<protocolName>"
    },
    "name": "ingravity_simulateDeepExploitAndWhitehatBounty"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeNoOptional Solidity (.sol) contract source code to include static exploit, honeypot, and slot0 manipulation analysis.
tierNoBilling & output depth: FULL ($45.00 USDC) returns flashLoanSimulation, liveOnChainPoolForensics, and unsigned Safe-Harbor rescue bundle; ESSENTIAL ($9.50 USDC) returns vulnerabilitySeverity, exploitImmunityScore, and summary counts only.FULL
tvlUsdNoDeclared pool TVL in USD; automatically overridden upward if live on-chain RPC TVL exceeds it.
chainIdNoTarget EVM chain ID for live RPC bytecode and TVL verification (8453 Base, 42161 Arbitrum, 10 Optimism, 137 Polygon, 1 Ethereum; unknown falls back to 8453).
poolAddressNoTarget 42-char EVM pool or vault contract address (0x...) inspected via live RPC on chainId.0x420DD381b31aEf6683db6B902084cB0FFECe40Da
protocolNameYesTarget protocol or pool identifier (non-empty string required).
ownerTreasuryNoOptional protocol owner/multisig recipient (0x...) receiving 90%-95% of assets in the generated unsigned Safe-Harbor calldata.

Output Schema

NameRequiredDescriptionDefault
tierYesService classification identifier ('institutional_whale_bounty').
actionYesRecommended exploit mitigation action.
signalYesTraffic-light severity indicator.
chainIdYesResolved EVM chain ID.
settledYesWhether x402 USDC payment settled cleanly.
summaryYesCritical/High severity counts, live TVL, and entitled whitehat bounty summary.
protocolYesEvaluated protocol identifier.
poolAddressYesTarget EVM pool or vault address inspected.
auditDetailsNoDetailed static audit findings when code is provided, or RPC summary note (FULL tier only).
tvlAnalyzedUsdYesEffective TVL used for whitehat bounty calculation.
whitehatRescuePlanNo90%-95% owner / 5%-10% whitehat split economics and private relay instructions (FULL tier only).
flashLoanSimulationNoSpot price oracle manipulation and reentrancy vector assessment (FULL tier only).
exploitImmunityScoreYesEstimated exploit immunity score from 0 to 100.
verifiedOnChainTvlUsdYesLive on-chain TVL verified via RPC (0 if unavailable or undeployed).
vulnerabilitySeverityYesOverall exploitability tier.
liveOnChainPoolForensicsNoLive RPC bytecode and proxy storage slot forensics for poolAddress (FULL tier only).
capitalSalvageAndSafeHarborNoUnsigned EIP-5792/EOA Safe-Harbor execution bundle (FULL tier only).
proportionalRescueCommissionPolicyNoAnti-Bypass and Safe-Harbor bounty policy metadata (FULL tier only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, but the description adds real behavior: it reads live RPC liquidity and optional Solidity source and never transfers funds. It further discloses billing enforcement ('unpaid calls return isError: true') and output sealing ('CRITICAL/HIGH PoCs stay sealed under Anti-Bypass') plus the 90-95%/5-10% rescue split, none of which is derivable from the annotations.

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

Conciseness4/5

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

Purpose and read-only guarantee are front-loaded, and nearly every clause carries operative information (defaults, tier pricing, sealing, alternative tool). It is dense and over-packed with parentheticals in a single long sentence, which makes parsing harder than necessary, but little is truly wasted.

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 an output schema and rich annotations, the description still covers the pieces an agent needs: cost/tier gating, failure mode on unpaid calls, scope of analysis, and the rescue-fund split. Nothing material 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.

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds useful cross-parameter meaning: poolAddress falls back to the Base Aerodrome address and tvlUsd defaults to 250000 while being overridden upward by live RPC TVL. It also frames ownerTreasury in terms of the bounty economics rather than just a recipient address.

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 a precise resource set: simulates flash-loan drain vectors, oracle slot0/reserve exposure, and live on-chain TVL across five EVM chains for a named protocol. It also explicitly separates itself from ingravity_generateMultiContractProtocolDossier for multi-file codebase audits, so an agent can route correctly without opening either 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 a concrete use case ('live pool exploitability and rescue planning') and names the sibling plus the condition that selects it (multi-file codebase audits). It also explains the FULL vs ESSENTIAL decision with prices and what each tier returns, which is the key branch point for calling this tool.

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.