get_debug_output

THE RISK

Low Risk

Why get_debug_output needs a policy

This tool retrieves existing debug output and error information from the Godot editor/project without creating, modifying, deleting, or executing any operations. It is a read-only query of diagnostic data, making it a Read category tool with low severity since debug output typically contains non-sensitive diagnostic information.

From the tool's definition Tool name 'get_debug_output' and description 'Get the current debug output and errors' indicate passive retrieval of debug logs and error messages with no modification or side effects.

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

POLICY

How to control get_debug_output

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 get_debug_output:

policy.json

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

get_debug_output is read-only, so it stays allowed — but 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.

CAP 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 connect_remote_debugger Connect to Godot editor\ 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

All 18 Godot MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_debug_output

What does the get_debug_output tool do? +

Get the current debug output and errors. It is categorised as a Read tool in the Godot MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_debug_output? +

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

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

Can I rate-limit get_debug_output? +

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

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

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