Run a guarded test command (allowlist/timeout; user_confirmed=true required) and return test result.
AI agents invoke run_tests to trigger actions in DumpAnalysisMCP. 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 runs arbitrary test commands on a system. Even with guards like allowlist restrictions and user confirmation, the ability to execute tests means an AI agent could invoke unintended test scenarios, potentially consuming resources, modifying test state, or triggering side effects. The requirement for user_confirmed=true provides procedural protection but does not eliminate execution risk.
From the tool's definition The tool 'run_tests' executes a test command. The description explicitly states it 'Run[s]' a test command, which triggers external operations whose effects depend on arguments.
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 DumpAnalysisMCP, 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 a guarded test command (allowlist/timeout; user_confirmed=true required) and return test result. It is categorised as a Execute tool in the DumpAnalysisMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DumpAnalysis 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 DumpAnalysisMCP. 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 DumpAnalysis MCP server (kindtis/dumpanalysismcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DumpAnalysisMCP, 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.
12 DumpAnalysisMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.