get_project_info
Get project metadata including name, version, engine version, and main scene
This record as markdown: /tools/keeveeg-godot-mcp/get-project-info.md
What get_project_info does on Godot
AI agents call get_project_info 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.
Why get_project_info is rated Low
This tool only retrieves and queries existing project metadata. It performs no writes, modifications, executions, deletions, or financial operations. The retrieval of project configuration data poses minimal security risk even if misused by an agent.
From the tool's definition Tool description states 'Get project metadata including name, version, engine version, and main scene' — pure retrieval of project information with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_project_info 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 get_project_info, this is the rule to start with:
get_project_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, apply this rule, and every get_project_info call is checked against it from then on.
Questions about get_project_info
Get project metadata including name, version, engine version, and main scene. It is categorised as a Read tool in the Godot MCP Server, which means it retrieves data without modifying state.
Register the Godot MCP server in PolicyLayer and add a rule for get_project_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. Nothing to install.
get_project_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 get_project_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 get_project_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.
get_project_info 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