AI agents invoke stop_run_instance to trigger actions in Godot Devtool. 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.
While not destructive of persistent data, stopping a runtime instance is an Execute action: it triggers termination of an external process/operation. The blast radius is high because an AI agent could halt critical game development workflows, interrupt debugging sessions, or terminate builds in progress.
From the tool's definition Stops a Godot run instance by runId — terminates a process/runtime execution. Description uses 'Stop', indicating it halts an active execution context. This is an external operation whose effects (process termination) depend on the runId argument.
Documented attack patterns abuse exactly the kind of access stop_run_instance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for stop_run_instance:
{
"version": "1",
"default": "deny",
"tools": {
"stop_run_instance": {
"limits": [
{
"counter": "stop_run_instance_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}stop_run_instance 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 one Godot run instance by runId. It is categorised as a Execute tool in the Godot Devtool MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for stop_run_instance: 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 Devtool. Nothing to install.
stop_run_instance 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_run_instance 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_run_instance. 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_run_instance is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.