This record as markdown: /tools/keeveeg-godot-mcp/set-remote-debug.md
What set_remote_debug does on Godot
AI agents use set_remote_debug 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 |
|---|---|---|---|
host | string | — | Debug host address (default: '127.0.0.1') |
port | integer | — | Debug port (default: 6007) |
enabled | boolean | Yes | Enable/disable remote debugging |
Parameters from the server's own tool schema.
Why set_remote_debug is rated Medium
This tool configures (writes/modifies) remote debugging settings for a Godot project. It sets up a connection configuration, which is a reversible write operation. It does not execute code directly, delete data, or involve financial transactions. Severity is medium because misconfiguration of remote debugging could expose the application to unintended remote access.
From the tool's definition set_remote_debug - 'Configure remote debugging connection'
Risk signalsAccepts URL/endpoint input (host)
Attacks that exploit this kind of access
The rule that runs set_remote_debug 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 set_remote_debug, this is the rule to start with:
set_remote_debug 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 set_remote_debug call is checked against it from then on.
Questions about set_remote_debug
Configure remote debugging connection. 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.
set_remote_debug accepts 3 parameters: host, port, enabled. Required: enabled. 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 set_remote_debug: 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.
set_remote_debug 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 set_remote_debug 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 set_remote_debug. 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.
set_remote_debug 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