run_test_scenario · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_test_scenario does on Godot MCP Server

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

WHY IT NEEDS A POLICY

Why run_test_scenario needs a policy

This tool triggers execution of test code in a running game instance. While not destructive or financial, it performs actions whose effects depend on the test scenario arguments provided—it could modify game state, trigger side effects, or cause unexpected behavior if a malicious test scenario is injected.

From the tool's definition Tool name 'run_test_scenario' combined with description 'Run a structured test scenario in the running game and collect results' indicates execution of game code/logic within the Godot runtime environment.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot MCP Server, so you can run agents against it safely.

FAQ

Questions about run_test_scenario

What does the run_test_scenario tool do? +

Run a structured test scenario in the running game and collect results. It is categorised as a Execute tool in the Godot MCP Server 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_test_scenario? +

Register the Godot MCP Server 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 MCP Server. 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 MCP server (neondeex/godotmcp-pro-free-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.