High Risk →

run_tests_json

run_tests_json

How to control run_tests_json ↓

What run_tests_json does on Mcp Debugpy

AI agents invoke run_tests_json to trigger actions in Mcp Debugpy. 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.

High Risk

Why run_tests_json needs a policy

Running tests is a form of code execution that triggers external operations (test runners) whose effects depend on test suite contents and environment. This constitutes Execute rather than Read or Write. Severity is high because test execution can modify system state (create temp files, call external services, modify databases), and an AI agent could run malicious or unvetted tests.

From the tool's definition Tool name 'run_tests_json' indicates execution of test suites. Server description states the MCP server enables 'AI agents to run tests' and uses debugpy/Debug Adapter Protocol.

Documented attack patterns abuse exactly the kind of access run_tests_json gives an agent:

How to control run_tests_json

PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Debugpy, and nothing reaches the server without passing your rules. This is the rule we recommend for run_tests_json:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_tests_json": {
      "limits": [
        {
          "counter": "run_tests_json_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

run_tests_json 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.

  1. Create a free account and register Mcp Debugpy — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about run_tests_json

What does the run_tests_json tool do? +

run_tests_json. It is categorised as a Execute tool in the Mcp Debugpy 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_json? +

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

What risk level is run_tests_json? +

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

Can I rate-limit run_tests_json? +

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

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

run_tests_json is provided by the Mcp Debugpy MCP server (markomanninen/mcp-debugpy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Debugpy tool call.

Start from Mcp Debugpy, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

16 Mcp Debugpy tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.