High Risk →

anvil_start

Start a new Anvil instance (local Ethereum node)

How to control anvil_start ↓

AI agents invoke anvil_start to trigger actions in Foundry MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Starting an Anvil instance is an Execute action because it launches and runs an external operation (an Ethereum node) whose effects are not immediately reversible without stopping the process. While it doesn't directly modify blockchain state, it sets up an execution environment for blockchain operations.

From the tool's definition Tool starts a new Anvil instance (local Ethereum node) - this initiates a process with external system effects that depend on arguments and configuration.

Documented attack patterns abuse exactly the kind of access anvil_start 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 anvil_start:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "anvil_start": {
      "limits": [
        {
          "counter": "anvil_start_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

anvil_start stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the anvil_start tool do? +

Start a new Anvil instance (local Ethereum node). It is categorised as a Execute tool in the Foundry MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on anvil_start? +

Register the Foundry MCP Server MCP server in PolicyLayer and add a rule for anvil_start: 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 anvil_start? +

anvil_start is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit anvil_start? +

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

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

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