run_test_scenario

Run a multi-step test scenario against the running game

SERVERGodot SOURCE@keeveeg/godot-mcp

High RISK CLASS

Category Execute

Parameters 21 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/run-test-scenario.md

WHAT IT DOES

What run_test_scenario does on Godot

AI agents invoke run_test_scenario to trigger actions in Godot. 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.

Parameter	Type	Required	Description
`name`	string	—	Scenario name (default: "Unnamed Scenario")
`steps`	array	Yes	Ordered test steps

Parameters from the server's own tool schema.

RISK

Why run_test_scenario is rated High

This tool triggers external operations (multi-step test scenarios) whose effects depend on the test scenario arguments and the current game state. It executes code/logic against a running process, which is characteristic of the Execute category. Severity is high because misconfigured or malicious test scenarios could crash the game, corrupt state, or trigger unintended gameplay behaviors.

From the tool's definition Tool name 'run_test_scenario' combined with description 'Run a multi-step test scenario against the running game' indicates execution of arbitrary test sequences against a live game instance.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs run_test_scenario safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_test_scenario, this is the rule to start with:

run_test_scenario Rate-limited

run_test_scenario 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_test_scenario": {
      "limits": [
        {
          "counter": "run_test_scenario_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every run_test_scenario call is checked against it from then on.

FAQ

Questions about run_test_scenario

What does the run_test_scenario tool do? +

Run a multi-step test scenario against the running game. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

What parameters does run_test_scenario accept? +

run_test_scenario accepts 2 parameters: name, steps. Required: steps. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on run_test_scenario? +

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

What risk level is run_test_scenario? +

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

Can I rate-limit run_test_scenario? +

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

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

run_test_scenario is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 321 Godot tools → High-risk tools on this server →

Across the catalogue

execute_test_case on Percepta MCP Server →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →