project_run_validation · LocalAnt MCP: Risk & Policy

WHAT IT DOES

What project_run_validation does on LocalAnt

AI agents invoke project_run_validation to trigger actions in LocalAnt. 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 project_run_validation needs a policy

Running a project can trigger arbitrary code execution, build scripts, tests, or external processes whose effects are unpredictable and depend on project configuration. While not destructive by default, the blast radius is high because a compromised project or malicious injection could exfiltrate data, modify files, or compromise the system.

From the tool's definition Tool name 'project_run_validation' with description 'Run the project' indicates execution of code or build processes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

project_run_validation Rate-limited

project_run_validation 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": {
    "project_run_validation": {
      "limits": [
        {
          "counter": "project_run_validation_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 LocalAnt, so you can run agents against it safely.

FAQ

Questions about project_run_validation

What does the project_run_validation tool do? +

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

How do I enforce a policy on project_run_validation? +

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

What risk level is project_run_validation? +

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

Can I rate-limit project_run_validation? +

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

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

project_run_validation is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.