Check GDScript files for errors after editing or when analyzing code.
AI agents call get_diagnostics to retrieve information from Minimal Godot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves diagnostic information about GDScript code without creating, modifying, deleting, or executing any files or operations. It is purely informational, analogous to a linter or static analyzer that reports problems without side effects. Even if an AI misuses it, the blast radius is minimal—the worst outcome is receiving diagnostic output.
From the tool's definition Tool description states 'Check GDScript files for errors' and 'syntax validation and diagnostics' — these are inspection/analysis operations with no modification.
Documented attack patterns abuse exactly the kind of access get_diagnostics gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Minimal Godot MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_diagnostics:
{
"version": "1",
"default": "deny",
"tools": {
"get_diagnostics": {}
}
}get_diagnostics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check GDScript files for errors after editing or when analyzing code. It is categorised as a Read tool in the Minimal Godot MCP MCP Server, which means it retrieves data without modifying state.
Register the Minimal Godot MCP server in PolicyLayer and add a rule for get_diagnostics: 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 Minimal Godot MCP. Nothing to install.
get_diagnostics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_diagnostics 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 get_diagnostics. 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.
get_diagnostics is provided by the Minimal Godot MCP server (ryanmazzolini/minimal-godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 4 Minimal Godot MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4 Minimal Godot MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.