stop_project

What stop_project does on Godot MCP

AI agents invoke stop_project to trigger actions in Godot MCP. 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 stop_project is rated High

The tool executes an action that terminates a running process. While not destructive (data is not deleted), it is Execute-category because it triggers an external operation with real-world side effects (process termination). Severity is medium because stopping a project interrupts workflow and may lose unsaved state, but does not permanently destroy data or move money.

From the tool's definition Tool description: 'Stop the currently running Godot project' — this triggers an external operation (halting a Godot process) whose effects depend on runtime state and cannot be trivially reversed without restarting.

The rule that runs stop_project safely

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

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_project": {
      "limits": [
        {
          "counter": "stop_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about stop_project