godot_stop
Terminate a managed process started by godot_run_managed.
This record as markdown: /tools/breakpoint-mcp/godot-stop.md
What godot_stop does on Breakpoint
AI agents invoke godot_stop to trigger actions in Breakpoint. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Process id from godot_run_managed |
Parameters from the server's own tool schema.
Why godot_stop is rated High
This tool executes an external operation (process termination) whose effects depend on which process is targeted. While termination itself is not destructive to data, it is an Execute category action because it triggers external system-level operations.
From the tool's definition Tool name 'godot_stop' and description 'Terminate a managed process started by godot_run_managed' indicates it stops/terminates processes, which is a form of process control execution.
Attacks that exploit this kind of access
The rule that runs godot_stop safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For godot_stop, this is the rule to start with:
godot_stop 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every godot_stop call is checked against it from then on.
Questions about godot_stop
Terminate a managed process started by godot_run_managed. It is categorised as a Execute tool in the Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
godot_stop accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for godot_stop: 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 Breakpoint. Nothing to install.
godot_stop 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 godot_stop 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 godot_stop. 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.
godot_stop is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
Across the catalogue