coverage_project · Foundry MCP Project MCP: Risk & Policy

WHAT IT DOES

What coverage_project does on Foundry MCP Project

AI agents invoke coverage_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 coverage_project needs a policy

Code coverage tools execute arbitrary test code and invoke external processes (coverage instrumentation, test runners). Although the tool does not modify contracts or move funds directly, it triggers execution of external operations whose side effects depend on project structure and test content. This is Execute, not Read, because it runs code rather than merely querying data.

From the tool's definition Tool name 'coverage_project' on a Foundry MCP server; description is empty. Based on sibling tools (build_project, run_script, run_cast_command_with_options, snapshot_project), this server executes development workflows.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

coverage_project Rate-limited

coverage_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": {
    "coverage_project": {
      "limits": [
        {
          "counter": "coverage_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 coverage_project

What does the coverage_project tool do? +

coverage_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 coverage_project? +

Register the Foundry MCP Project MCP server in PolicyLayer and add a rule for coverage_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 coverage_project? +

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

Can I rate-limit coverage_project? +

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

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

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