godot_stop

Terminate a managed process started by godot_run_managed.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/godot-breakpoint-mcp/godot-stop.md

WHAT IT DOES

What godot_stop does on Godot Breakpoint

AI agents invoke godot_stop to trigger actions in Godot 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.

RISK

Why godot_stop is rated High

Terminating a process is an Execute action—it triggers an external operation whose effects depend on which process is being terminated. While not destructive to data, it can disrupt game development workflows or running applications.

From the tool's definition Tool description states 'Terminate a managed process started by godot_run_managed', which is an external operation that stops a running process.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs godot_stop safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Godot 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 Rate-limited

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.

View as policy code

policy.json

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

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every godot_stop call is checked against it from then on.

FAQ

Questions about godot_stop

What does the godot_stop tool do? +

Terminate a managed process started by godot_run_managed. It is categorised as a Execute tool in the Godot Breakpoint MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on godot_stop? +

Register the Godot 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 Godot Breakpoint. Nothing to install.

What risk level is godot_stop? +

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

Can I rate-limit godot_stop? +

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.

How do I block godot_stop completely? +

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.

What MCP server provides godot_stop? +

godot_stop is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Godot Breakpoint, and thousands of servers like it.

This server

All 239 Godot Breakpoint tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →