// SCAN REPORT

Foundry MCP Project

12 tools. 10 can modify or destroy data without limits.

10 write tools that can modify data. Rate limits recommended.

Last updated: 30 Jun 2026

10 can modify or destroy data

2 read-only

12 tools total

Community server · catalogue entry verified 30/06/2026

How to control Foundry MCP Project ↓

TOOL MAP

What Foundry MCP Project exposes to your agents

Read (2) Write / Execute (10) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Foundry MCP Project tools

Execute · High build_project Build operations execute code compilation and potentially code generation in an Ethereum development environment (Foundry). Execute · High clone_contract While cloning itself is fundamentally a retrieval operation (Read), the purpose is to obtain smart contract code for execution in a Foundry environment where it can be run, tested, or deployed. Execute · High coverage_project Code coverage tools execute arbitrary test code and invoke external processes (coverage instrumentation, test runners). Execute · High run_cast_command_with_options The tool runs cast commands with configurable options, which is Execute-category behavior—it triggers external operations (blockchain interactions, contract calls) whose effects depend on the command arguments supplied.

10 of Foundry MCP Project's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Foundry MCP Project

PolicyLayer is an MCP gateway — it sits between your AI agents and Foundry MCP Project, and nothing reaches the server without passing your rules. These are the rules we recommend:

Rate limit write operations

{
  "create_project": {
    "limits": [
      {
        "counter": "create_project_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "inspect_contract": {
    "limits": [
      {
        "counter": "inspect_contract_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Foundry MCP Project — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FOUNDRY MCP PROJECT →

Instant setup, no code required.

FULL CATALOGUE

All 12 Foundry MCP Project tools

EXECUTE 9 tools

Execute build_project build_project Execute clone_contract Clones a contract from Etherscan with specified options. Execute coverage_project coverage_project Execute run_cast_command_with_options run_cast_command_with_options Execute run_script Runs a script in the current Foundry project. Execute run_script_with_options run_script_with_options Execute start_anvil_with_options start_anvil_with_options Execute start_chisel_with_options start_chisel_with_options Execute test_project test_project

WRITE 1 tools

Write create_project Creates a new Foundry project.

READ 2 tools

Read inspect_contract inspect_contract Read snapshot_project snapshot_project

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Foundry MCP Project

How do I prevent bulk modifications through Foundry MCP Project? +

The Foundry MCP Project server has 1 write tools including create_project. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Foundry MCP Project.

How many tools does the Foundry MCP Project MCP server expose? +

12 tools across 3 categories: Execute, Read, Write. 2 are read-only. 10 can modify, create, or delete data.

How do I enforce a policy on Foundry MCP Project? +

Register the Foundry MCP Project MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Foundry MCP Project tool call.

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

ENFORCE POLICY ON FOUNDRY MCP PROJECT →

Instant setup, no code required.

12 Foundry MCP Project tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Foundry MCP Project's registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →