Stop the currently running Godot project
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.
This tool executes a command to halt an active process, which is an operational control action (similar to kill, terminate, or shutdown commands). While not destructive (no data is deleted), it is not merely reading or writing data—it actively triggers external operations whose effects depend on system state.
From the tool's definition Tool description states 'Stop the currently running Godot project' — this is an action that terminates a process and affects the state of the running application.
Documented attack patterns abuse exactly the kind of access stop_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_project:
{
"version": "1",
"default": "deny",
"tools": {
"stop_project": {
"limits": [
{
"counter": "stop_project_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
Stop the currently running Godot project. It is categorised as a Execute tool in the Godot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot 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. Nothing to install.
stop_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
stop_project is provided by the Godot MCP server (leesinliang/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
18 Godot MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.