editor_remove_breakpoint · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_remove_breakpoint does on Godot

AI agents use editor_remove_breakpoint to create or update resources in Godot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.

PARAMETERS

Parameter	Type	Required	Description
`line`	number	Yes	Line number
`script`	string	Yes	Script path

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_remove_breakpoint needs a policy

Removing a breakpoint modifies editor/debug state in a reversible way (breakpoints can be re-added). It does not delete data, execute code, or have financial implications. This is a write/modification of debugging configuration.

From the tool's definition Remove a breakpoint from a script

Risk signalsAccepts freeform code/query input (script)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_remove_breakpoint Rate-limited

editor_remove_breakpoint stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_remove_breakpoint": {
      "limits": [
        {
          "counter": "editor_remove_breakpoint_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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, so you can run agents against it safely.

FAQ

Questions about editor_remove_breakpoint

What does the editor_remove_breakpoint tool do? +

Remove a breakpoint from a script. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does editor_remove_breakpoint accept? +

editor_remove_breakpoint accepts 2 parameters: line, script. Required: line, script. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_remove_breakpoint? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_remove_breakpoint: 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. Nothing to install.

What risk level is editor_remove_breakpoint? +

editor_remove_breakpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit editor_remove_breakpoint? +

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

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

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