export_project · Godot MCP: Risk & Policy

WHAT IT DOES

What export_project does on Godot

AI agents invoke export_project 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.

PARAMETERS

Parameter	Type	Required	Description
`preset`	string	Yes	Export preset name (as defined in your export_presets.cfg, e.g. "Windows Desktop", "Linux/X11")
`output_path`	string	Yes	Output file path (absolute or relative) for the exported build
`project_path`	object	—	Project path (default: current project root)

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why export_project needs a policy

This tool triggers a Godot CLI execution to export a project, which runs an external process/command. While it produces an output artifact (exported game), it executes an external CLI operation whose effects depend on the preset arguments.

From the tool's definition Export project via Godot CLI preset

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

export_project Rate-limited

export_project 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "export_project": {
      "limits": [
        {
          "counter": "export_project_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Godot, so you can run agents against it safely.

FAQ

Questions about export_project

What does the export_project tool do? +

Export project via Godot CLI preset. 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.

What parameters does export_project accept? +

export_project accepts 3 parameters: preset, output_path, project_path. Required: preset, output_path. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on export_project? +

Register the Godot MCP server in PolicyLayer and add a rule for export_project: 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 export_project? +

export_project is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit export_project? +

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

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

export_project is provided by the Godot MCP server (@yanhuifair/godot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.