connect_remote_debugger

THE RISK

High Risk

Why connect_remote_debugger needs a policy

Connecting a remote debugger establishes an active session with the Godot editor's debug interface, which is an external operation with side effects (attaching a debugger process). It doesn't merely read data, nor does it destroy or write content — it executes a connection/attachment action.

From the tool's definition Connect to Godot editor — initiates a connection to a remote debugger, triggering an external operation

Documented attack patterns abuse exactly the kind of access connect_remote_debugger gives an agent:

POLICY

How to control connect_remote_debugger

PolicyLayer is an MCP gateway — it sits between your AI agents and Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for connect_remote_debugger:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "connect_remote_debugger": {
      "limits": [
        {
          "counter": "connect_remote_debugger_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

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

Create a free account and register Godot MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Godot MCP tools

Execute launch_editor Launch Godot editor for a specific project Execute run_project Run the Godot project and capture output Execute stop_project Stop the currently running Godot project Execute disconnect_remote_debugger Disconnect from the Godot editor\ Write load_sprite Load a sprite into a Sprite2D node Write add_node Add a node to an existing scene Write create_scene Create a new Godot scene file Write export_mesh_library Export a scene as a MeshLibrary resource

All 18 Godot MCP tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in Godot MCP → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about connect_remote_debugger

What does the connect_remote_debugger tool do? +

Connect to Godot editor\. It is categorised as a Execute tool in the Godot MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on connect_remote_debugger? +

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

What risk level is connect_remote_debugger? +

connect_remote_debugger is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit connect_remote_debugger? +

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

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

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

Enforce policy on every Godot MCP tool call.

Start from Godot MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →