project_stop

What project_stop does on Godot

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

Why project_stop is rated High

Stopping a running project is an Execute action because it triggers an external operation (process termination) whose effects depend on context (which project is running). It is not Read (no data retrieval), Write (not creating/modifying persistent data reversibly), Destructive (stopping a process is not irreversible), Financial (no money involved), or Other.

From the tool's definition Tool performs 'Stop the currently running Godot project' — an action that terminates a running process. This is an operational control that triggers external execution with side effects dependent on the running state, similar to process termination or system…

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

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

Questions about project_stop