run_all_tests · Local Testing Agent MCP Server MCP

WHAT IT DOES

What run_all_tests does on Local Testing Agent MCP Server

AI agents invoke run_all_tests to trigger actions in Local Testing Agent MCP Server. 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_all_tests needs a policy

This tool runs automated tests across a codebase, which constitutes execution of arbitrary code whose effects (test results, side effects, logging, output) depend on the test suite content and repository state. While testing is generally benign, it remains an Execute category tool because it invokes code execution with potentially unpredictable outcomes.

From the tool's definition Tool name 'run_all_tests' combined with server description indicating 'automated test execution' and sibling tools like 'run_all_tests_parallel' and 'full_phase2_pipeline' clearly show this executes code/tests.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_all_tests Rate-limited

run_all_tests 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_all_tests": {
      "limits": [
        {
          "counter": "run_all_tests_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 Local Testing Agent MCP Server, so you can run agents against it safely.

FAQ

Questions about run_all_tests

What does the run_all_tests tool do? +

Phase 2 – Option B:. It is categorised as a Execute tool in the Local Testing Agent MCP Server 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_all_tests? +

Register the Local Testing Agent MCP Server MCP server in PolicyLayer and add a rule for run_all_tests: 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 Local Testing Agent MCP Server. Nothing to install.

What risk level is run_all_tests? +

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

Can I rate-limit run_all_tests? +

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

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

run_all_tests is provided by the Local Testing Agent MCP Server MCP server (marcelkurvers/local-testing-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.