project_get_info
Return project name, main scene, project root path, Godot version, and feature tags.
This record as markdown: /tools/godot-breakpoint-mcp/project-get-info.md
What project_get_info does on Godot Breakpoint
AI agents call project_get_info to retrieve information from Godot Breakpoint without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why project_get_info is rated Low
This tool retrieves project metadata and configuration information without creating, modifying, deleting, or executing any operations. It is purely informational and has no capability to alter state or trigger external actions. The blast radius of misuse is minimal—exposing project metadata is a read-only operation.
From the tool's definition Tool name 'project_get_info' and description states it 'Return[s] project name, main scene, project root path, Godot version, and feature tags.' The verb 'return' and 'get' indicate data retrieval with no modification or side effects.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs project_get_info safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Godot Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For project_get_info, this is the rule to start with:
project_get_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot Breakpoint, apply this rule, and every project_get_info call is checked against it from then on.
Questions about project_get_info
Return project name, main scene, project root path, Godot version, and feature tags. It is categorised as a Read tool in the Godot Breakpoint MCP Server, which means it retrieves data without modifying state.
Register the Godot Breakpoint MCP server in PolicyLayer and add a rule for project_get_info: 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 Breakpoint. Nothing to install.
project_get_info 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 project_get_info 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 project_get_info. 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.
project_get_info is provided by the Godot Breakpoint MCP server (jlivingston-Cipher/godot-breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Godot Breakpoint, and thousands of servers like it.
This server
Across the catalogue