run_tests

Run tests using appropriate test runner

SERVERCode MCP Server SOURCEagentics-ai/code-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/agentics-ai-code-mcp/run-tests.md

WHAT IT DOES

What run_tests does on Code MCP Server

AI agents invoke run_tests to trigger actions in Code 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.

RISK

Why run_tests is rated High

This tool triggers test execution, which is a form of code execution that can have side effects depending on the test suite (e.g., tests may modify files, call external APIs, or trigger infrastructure changes). While primarily intended for testing, an AI agent could misuse it to execute arbitrary code if test files are controlled or modified.

From the tool's definition The tool runs tests using test runners, which executes code in the workspace environment. The description explicitly states 'Run tests using appropriate test runner', indicating arbitrary code execution through test infrastructure.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_tests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Code MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_tests, this is the rule to start with:

run_tests Rate-limited

run_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_tests": {
      "limits": [
        {
          "counter": "run_tests_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Code MCP Server, apply this rule, and every run_tests call is checked against it from then on.

FAQ

Questions about run_tests

What does the run_tests tool do? +

Run tests using appropriate test runner. It is categorised as a Execute tool in the Code 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_tests? +

Register the Code MCP Server MCP server in PolicyLayer and add a rule for run_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 Code MCP Server. Nothing to install.

What risk level is run_tests? +

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

Can I rate-limit run_tests? +

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

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

run_tests is provided by the Code MCP Server MCP server (agentics-ai/code-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Code MCP Server, and thousands of servers like it.

This server

All 73 Code MCP Server tools → High-risk tools on this server →

Across the catalogue

shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →