editor_ping

Check that the editor is running with the Breakpoint MCP plugin enabled.

SERVERGodot Breakpoint SOURCEjlivingston-Cipher/godot-breakpoint-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/godot-breakpoint-mcp/editor-ping.md

WHAT IT DOES

What editor_ping does on Godot Breakpoint

AI agents call editor_ping to retrieve information from Godot Breakpoint 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_ping is rated Low

This tool only verifies that the Godot editor is running with the plugin enabled. It is a read-only health/status check that retrieves state information without modifying anything.

From the tool's definition "Check that the editor is running" — purely a status/health check with no side effects

Attacks that exploit this kind of access

RECOMMENDED RULE

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

editor_ping Allowed

editor_ping 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_ping": {}
  }
}

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

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

FAQ

Questions about editor_ping

What does the editor_ping tool do? +

Check that the editor is running with the Breakpoint MCP plugin enabled. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on editor_ping? +

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

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

Can I rate-limit editor_ping? +

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

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

editor_ping 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 →

Across the catalogue

The MCP Attack Database →

Guides

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