AI agents invoke run_tests to trigger actions in MCP DevTools 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.
This tool executes test code in the repository, which is an Execute action. While tests are typically safe, they can have side effects (database modifications, file I/O, network calls, etc.). An AI agent with access to this tool could trigger tests that modify system state, create resources, or interact with external services.
From the tool's definition Tool is named 'run_tests' and described as 'Run tests using the detected test framework'. The verb 'Run' combined with 'detected test framework' indicates execution of arbitrary code (test suites) whose behavior depends on what tests exist in the project.
Documented attack patterns abuse exactly the kind of access run_tests gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP DevTools Server, and nothing reaches the server without passing your rules. This is the rule we recommend for run_tests:
{
"version": "1",
"default": "deny",
"tools": {
"run_tests": {
"limits": [
{
"counter": "run_tests_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Run tests using the detected test framework. It is categorised as a Execute tool in the MCP DevTools Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MCP DevTools 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 MCP DevTools Server. Nothing to install.
run_tests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
run_tests is provided by the MCP DevTools Server MCP server (rshade/mcp-devtools-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP DevTools Server, 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.
79 MCP DevTools Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.