debugger_set_breakpoint
Define breakpoint. Ex: {
This record as markdown: /tools/mcp-godot-desenvolvimento/debugger-set-breakpoint.md
What debugger_set_breakpoint does on Mcp Godot Desenvolvimento
AI agents invoke debugger_set_breakpoint to trigger actions in Mcp Godot Desenvolvimento. 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.
Why debugger_set_breakpoint is rated High
Setting a breakpoint is an action that affects the execution state of a running or debuggable program. It modifies the runtime behavior (pausing execution at a given point), which falls under Execute rather than a simple data read or write. The description is truncated/uninformative ('Ex: {'), which lowers confidence slightly, but the tool name clearly implies debugger control.
From the tool's definition debugger_set_breakpoint — sets a breakpoint in the debugger, triggering/controlling execution flow in the Godot runtime debug environment
Attacks that exploit this kind of access
The rule that runs debugger_set_breakpoint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Godot Desenvolvimento, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For debugger_set_breakpoint, this is the rule to start with:
debugger_set_breakpoint 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 Mcp Godot Desenvolvimento, apply this rule, and every debugger_set_breakpoint call is checked against it from then on.
Questions about debugger_set_breakpoint
Define breakpoint. Ex: {. It is categorised as a Execute tool in the Mcp Godot Desenvolvimento MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Godot Desenvolvimento MCP server in PolicyLayer and add a rule for debugger_set_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 Mcp Godot Desenvolvimento. Nothing to install.
debugger_set_breakpoint 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 debugger_set_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 debugger_set_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.
debugger_set_breakpoint is provided by the Mcp Godot Desenvolvimento MCP server (joabcostamd/mcp-godot-desenvolvimento). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Godot Desenvolvimento, and thousands of servers like it.
Across the catalogue