test_run · Universal Dev MCP: Risk & Policy

WHAT IT DOES

What test_run does on Universal Dev MCP

AI agents invoke test_run to trigger actions in Universal Dev MCP. 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_run needs a policy

Running test suites executes arbitrary code in the project environment. While typically benign, tests can have side effects (database writes, file I/O, network calls, seed scripts). The auto-detection of multiple frameworks (pytest/jest/phpunit) indicates dynamic execution. Severity is medium because tests are usually sandboxed but can have real side effects depending on project configuration.

From the tool's definition 'test_run' with description 'Tests chalana (auto-detect: pytest/jest/phpunit)' — runs test frameworks (pytest, jest, phpunit) which execute code in the project environment

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

test_run Rate-limited

test_run 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_run": {
      "limits": [
        {
          "counter": "test_run_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 Universal Dev MCP, so you can run agents against it safely.

FAQ

Questions about test_run

What does the test_run tool do? +

Tests chalana (auto-detect: pytest/jest/phpunit). It is categorised as a Execute tool in the Universal Dev MCP 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_run? +

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

What risk level is test_run? +

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

Can I rate-limit test_run? +

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

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

test_run is provided by the Universal Dev MCP server (kallusuvaidyam/universal_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.