project_get_debug_output

Get the current debug output and errors.

SERVERGodot SOURCEchanceflow/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/chanceflow-godot-mcp/project-get-debug-output.md

WHAT IT DOES

What project_get_debug_output does on Godot

AI agents call project_get_debug_output 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 project_get_debug_output is rated Low

This tool retrieves and queries debug output and error logs from a running Godot project. It performs a read-only operation—fetching diagnostic information that already exists—without creating, modifying, deleting, or executing any code.

From the tool's definition Tool name 'project_get_debug_output' and description 'Get the current debug output and errors' indicate retrieval of existing log/debug data with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

project_get_debug_output Allowed

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

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 project_get_debug_output call is checked against it from then on.

FAQ

Questions about project_get_debug_output

What does the project_get_debug_output tool do? +

Get the current debug output and errors. 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 project_get_debug_output? +

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

What risk level is project_get_debug_output? +

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

Can I rate-limit project_get_debug_output? +

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

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

project_get_debug_output is provided by the Godot MCP server (chanceflow/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 84 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 →