remove_breakpoint
Remove a breakpoint from a GDScript file at a specific line
This record as markdown: /tools/keeveeg-godot-mcp/remove-breakpoint.md
What remove_breakpoint does on Godot
AI agents use 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
line | integer | Yes | Line number of the breakpoint to remove |
script_path | string | Yes | Script file path (e.g. 'res://scripts/player.gd') |
Parameters from the server's own tool schema.
Why remove_breakpoint is rated Medium
Removing a breakpoint modifies the debug configuration of a GDScript file, but this is a reversible operation (breakpoints can be re-added). It doesn't delete code or data, just changes debugging state. Classified as Write rather than Destructive because breakpoints can be restored easily.
From the tool's definition Remove a breakpoint from a GDScript file at a specific line
Attacks that exploit this kind of access
The rule that runs remove_breakpoint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_breakpoint, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every remove_breakpoint call is checked against it from then on.
Questions about remove_breakpoint
Remove a breakpoint from a GDScript file at a specific line. 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.
remove_breakpoint accepts 2 parameters: line, script_path. Required: line, script_path. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for 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.
remove_breakpoint is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the 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.
Set action: deny in the PolicyLayer policy for 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.
remove_breakpoint is provided by the Godot MCP server (@keeveeg/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot, and thousands of servers like it.
This server
Across the catalogue