Generate visual control flow graph for EVM bytecode using Heimdall
AI agents call heimdall_cfg 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.
The tool performs static analysis of bytecode to generate a graph visualization. Reading and analyzing existing bytecode without side effects is a Read operation. No data is created, modified, deleted, or financial transactions occur. The blast radius of misuse is minimal—worst case an agent requests analysis of arbitrary bytecode, which presents no risk to system state or funds.
From the tool's definition Generates a visual control flow graph (CFG) for EVM bytecode. This is an analytical/visualization tool that reads and analyzes bytecode without executing it, sending transactions, or modifying state.
Documented attack patterns abuse exactly the kind of access heimdall_cfg 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_cfg:
{
"version": "1",
"default": "deny",
"tools": {
"heimdall_cfg": {}
}
}heimdall_cfg is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Generate visual control flow graph for EVM bytecode using Heimdall. It is categorised as a Read tool in the Foundry MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Foundry MCP Server MCP server in PolicyLayer and add a rule for heimdall_cfg: 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.
heimdall_cfg 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 heimdall_cfg 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 heimdall_cfg. 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.
heimdall_cfg 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.
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.