test_project · Foundry MCP Project MCP: Risk & Policy

WHAT IT DOES

What test_project does on Foundry MCP Project

AI agents invoke test_project to trigger actions in Foundry MCP Project. 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.

WHY IT NEEDS A POLICY

Why test_project needs a policy

Based on the server context (Foundry Ethereum development environment) and sibling tools like 'build_project', 'run_script', and 'coverage_project', 'test_project' almost certainly runs the Foundry test suite (e.g., 'forge test'). This executes code/scripts against smart contracts, which can have side effects depending on test configurations. Empty description lowers confidence.

From the tool's definition Tool name 'test_project' on a server for Foundry Ethereum development; description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_project Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "test_project": {
      "limits": [
        {
          "counter": "test_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Foundry MCP Project, so you can run agents against it safely.

FAQ

Questions about test_project

What does the test_project tool do? +

test_project. It is categorised as a Execute tool in the Foundry MCP Project MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on test_project? +

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

What risk level is test_project? +

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

Can I rate-limit test_project? +

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

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

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