High Risk →

run_scenario_test

Run a specific test scenario and get detailed results.

Single-target operation

Part of the Test Genie MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

test-genie-mcp Execute Risk 3/5

AI agents invoke run_scenario_test to trigger processes or run actions in Test Genie. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

run_scenario_test can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

io-github-muse-code-space-test-genie.yaml
tools:
  run_scenario_test:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Test Genie policy for all 19 tools.

Tool Name run_scenario_test
Category Execute
Risk Level High

View all 19 tools →

Agents calling execute-class tools like run_scenario_test have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

run_scenario_test is one of the high-risk operations in Test Genie. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the run_scenario_test tool do? +

Run a specific test scenario and get detailed results.. It is categorised as a Execute tool in the Test Genie 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_scenario_test? +

Add a rule in your Intercept YAML policy under the tools section for run_scenario_test. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Test Genie MCP server.

What risk level is run_scenario_test? +

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

Can I rate-limit run_scenario_test? +

Yes. Add a rate_limit block to the run_scenario_test rule in your Intercept 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_scenario_test completely? +

Set action: deny in the Intercept policy for run_scenario_test. 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_scenario_test? +

run_scenario_test is provided by the Test Genie MCP server (test-genie-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Test Genie

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.