This record as markdown: /tools/chanceflow-godot-mcp/project-export.md
What project_export does on Godot
AI agents invoke project_export to trigger actions in Godot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why project_export is rated High
The description is empty, so classification is based on name alone. 'project_export' in the context of a Godot game engine integration most likely triggers a Godot export build process — compiling and packaging a project — which constitutes executing an external operation. This is an Execute-level action. Confidence is moderate due to the empty description.
From the tool's definition Tool name 'project_export' on a Godot MCP server described as enabling interaction with the Godot game engine including launching editor and running projects.
Attacks that exploit this kind of access
The rule that runs project_export 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_export, this is the rule to start with:
project_export stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 project_export call is checked against it from then on.
Questions about project_export
project_export is a execute tool on the Godot MCP server. It is categorised as a Execute tool in the Godot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot MCP server in PolicyLayer and add a rule for project_export: 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.
project_export is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the project_export 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_export. 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_export 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue