This record as markdown: /tools/yanhuifair-godot-mcp/add-script-export.md
What add_script_export does on Godot
AI agents use add_script_export to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Path to .gd script file |
var_name | string | Yes | Variable name |
var_type | object | — | Type hint |
export_hint | object | — | Export hint (e.g. "int, 0, 100") |
default_value | object | — | Default value |
Parameters from the server's own tool schema.
Why add_script_export is rated Medium
This tool modifies GDScript source code by adding a new @export variable declaration. This is a Write operation because it creates/modifies data (script files) reversibly—the change can be undone by removing the export declaration. It does not execute code, delete data irreversibly, or move money.
From the tool's definition Tool name 'add_script_export' and description 'Add @export variable to GDScript' indicate creation/modification of script properties.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs add_script_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 add_script_export, this is the rule to start with:
add_script_export stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 add_script_export call is checked against it from then on.
Questions about add_script_export
Add @export variable to GDScript. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
add_script_export accepts 5 parameters: path, var_name, var_type, export_hint, default_value. Required: path, var_name. The full parameter table on this page comes from the server's own tool schema.
Register the Godot MCP server in PolicyLayer and add a rule for add_script_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.
add_script_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_script_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 add_script_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.
add_script_export 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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue