run_generated_tests · Decide Test MCP: Risk & Policy

WHAT IT DOES

What run_generated_tests does on Decide Test MCP

AI agents invoke run_generated_tests to trigger actions in Decide Test 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 run_generated_tests needs a policy

This tool executes code (Playwright and API tests) whose behavior depends on the test cases provided. While tests are typically non-destructive in intent, they can perform arbitrary actions: API calls with side effects, browser interactions that modify external state, or database operations.

From the tool's definition Tool name and description: 'run_generated_tests' - 'Execute generated tests and return results'. The verb 'Execute' is explicit, and the server context indicates this runs Playwright/API test code.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_generated_tests Rate-limited

run_generated_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_generated_tests": {
      "limits": [
        {
          "counter": "run_generated_tests_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 Decide Test MCP, so you can run agents against it safely.

FAQ

Questions about run_generated_tests

What does the run_generated_tests tool do? +

Execute generated tests and return results. It is categorised as a Execute tool in the Decide Test 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 run_generated_tests? +

Register the Decide Test MCP server in PolicyLayer and add a rule for run_generated_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 Decide Test MCP. Nothing to install.

What risk level is run_generated_tests? +

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

Can I rate-limit run_generated_tests? +

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

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

run_generated_tests is provided by the Decide Test MCP server (k-n-t-lam/decide-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.