stop_project · Godot MCP Server MCP: Risk & Policy

WHAT IT DOES

What stop_project does on Godot MCP Server

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

This tool triggers an external operation (process termination) whose effects depend on which project is targeted. While not destructive to data, it interrupts running game engine operations and constitutes an Execute action. Severity is medium because the blast radius is limited to stopping a specific project instance rather than system-wide impact, and the action is reversible by relaunching the project.

From the tool's definition Tool name 'stop_project' indicates termination of a running process. Sibling context shows tools that 'launch_editor' and 'run_project', confirming this server manages process lifecycle. Stopping a project terminates execution with external effects.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stop_project Rate-limited

stop_project 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_project": {
      "limits": [
        {
          "counter": "stop_project_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 stop_project

What does the stop_project tool do? +

stop_project. 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 stop_project? +

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

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

Can I rate-limit stop_project? +

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

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

stop_project is provided by the Godot MCP Server MCP server (matula/godot-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.