run_project_checks · Mcp Flow MCP: Risk & Policy

WHAT IT DOES

What run_project_checks does on Mcp Flow

AI agents invoke run_project_checks to trigger actions in Mcp Flow. 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 run_project_checks needs a policy

The tool runs project checks/tests, which involves executing code external to the MCP server—a classic Execute category action. Severity is high because misconfigured or malicious project check scripts could cause significant unintended effects (resource exhaustion, data corruption, credential exposure).

From the tool's definition Tool description states 'run the project' which triggers execution of external operations. Combined with context that this is a 'software-development loop' server with tools like 'apply_patch' and 'fix_loop', this tool executes build/test commands or scripts…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_project_checks Rate-limited

run_project_checks 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": {
    "run_project_checks": {
      "limits": [
        {
          "counter": "run_project_checks_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 Mcp Flow, so you can run agents against it safely.

FAQ

Questions about run_project_checks

What does the run_project_checks tool do? +

Auto-detect and run the project. It is categorised as a Execute tool in the Mcp Flow MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_project_checks? +

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

What risk level is run_project_checks? +

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

Can I rate-limit run_project_checks? +

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

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

run_project_checks is provided by the Mcp Flow MCP server (remimenguy/mcp-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.