editor_get_breakpoints

List all breakpoints.

SERVERGodot SOURCE@yanhuifair/godot-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/yanhuifair-godot-mcp/editor-get-breakpoints.md

WHAT IT DOES

What editor_get_breakpoints does on Godot

AI agents call editor_get_breakpoints to retrieve information from Godot without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why editor_get_breakpoints is rated Low

This tool queries and returns breakpoint information from the Godot editor without modifying, executing, or deleting any data. It is a read-only introspection capability typical of debugger APIs. The blast radius of misuse is minimal; an agent could only gain visibility into debugging state.

From the tool's definition Tool name is 'editor_get_breakpoints' and description states 'List all breakpoints' — a pure retrieval operation with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs editor_get_breakpoints 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 editor_get_breakpoints, this is the rule to start with:

editor_get_breakpoints Allowed

editor_get_breakpoints is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "editor_get_breakpoints": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about editor_get_breakpoints

What does the editor_get_breakpoints tool do? +

List all breakpoints. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_get_breakpoints? +

Register the Godot MCP server in PolicyLayer and add a rule for editor_get_breakpoints: 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_get_breakpoints? +

editor_get_breakpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit editor_get_breakpoints? +

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

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

editor_get_breakpoints 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.

KEEP EXPLORING

More on Godot, and thousands of servers like it.

This server

All 282 Godot tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →