stop_scene

Stop the currently playing scene

SERVERGodot SOURCE@keeveeg/godot-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/keeveeg-godot-mcp/stop-scene.md

WHAT IT DOES

What stop_scene does on Godot

AI agents invoke stop_scene 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.

RISK

Why stop_scene is rated High

This tool executes a control command that stops an active scene, which is an irreversible runtime action with side effects on the game state. While not destructive (data is not deleted), it is an Execute action as it triggers an external operation (scene state change) whose effects depend on the current application context. The high severity reflects that misuse could disrupt game sessions or workflows.

From the tool's definition Tool name 'stop_scene' and description 'Stop the currently playing scene' indicate an action that triggers a runtime operation in the Godot game engine.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_scene 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 stop_scene, this is the rule to start with:

stop_scene Rate-limited

stop_scene 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": {
    "stop_scene": {
      "limits": [
        {
          "counter": "stop_scene_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 stop_scene call is checked against it from then on.

FAQ

Questions about stop_scene

What does the stop_scene tool do? +

Stop the currently playing scene. 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.

How do I enforce a policy on stop_scene? +

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

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

Can I rate-limit stop_scene? +

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

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

stop_scene 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

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

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