Low Risk

heimdall_decompile

Decompile EVM bytecode to Solidity source code and ABI using Heimdall

How to control heimdall_decompile ↓

AI agents call heimdall_decompile to retrieve information from Foundry MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool performs a read/analysis operation — it takes EVM bytecode as input and produces decompiled Solidity source code and ABI as output. It does not modify state, execute transactions, delete data, or move funds. It is a pure analysis/reverse-engineering tool with no side effects on chain or local state.

From the tool's definition Decompile EVM bytecode to Solidity source code and ABI using Heimdall

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

PolicyLayer is an MCP gateway — it sits between your AI agents and Foundry MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for heimdall_decompile:

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

heimdall_decompile 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 Foundry 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.

Go deeper

What does the heimdall_decompile tool do? +

Decompile EVM bytecode to Solidity source code and ABI using Heimdall. It is categorised as a Read tool in the Foundry MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on heimdall_decompile? +

Register the Foundry MCP Server MCP server in PolicyLayer and add a rule for heimdall_decompile: 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 Foundry MCP Server. Nothing to install.

What risk level is heimdall_decompile? +

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

Can I rate-limit heimdall_decompile? +

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

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

heimdall_decompile is provided by the Foundry MCP Server MCP server (praneshasp/foundry-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Foundry MCP Server tool call.

Deterministic rules across all 16 Foundry MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

16 Foundry MCP Server tools catalogued and risk-classified — across an index of 42,500+ 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.