run_stress_test · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What run_stress_test does on Godot MCP Server

AI agents invoke run_stress_test 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_stress_test needs a policy

This tool executes a predefined stress test operation in the Godot editor, which triggers game engine processing and performance monitoring whose effects and resource consumption depend on test parameters.

From the tool's definition Tool name 'run_stress_test' combined with description stating 'Run a stress test scenario and collect performance data over time' indicates execution of a defined test scenario within the Godot engine.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_stress_test Rate-limited

run_stress_test 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_stress_test": {
      "limits": [
        {
          "counter": "run_stress_test_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_stress_test

What does the run_stress_test tool do? +

Run a stress test scenario and collect performance data over time. 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_stress_test? +

Register the Godot MCP Server MCP server in PolicyLayer and add a rule for run_stress_test: 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_stress_test? +

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

Can I rate-limit run_stress_test? +

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

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

run_stress_test 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.