add_script_export · Godot MCP: Risk & Policy

WHAT IT DOES

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.

PARAMETERS

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 IT NEEDS A POLICY

Why add_script_export needs a policy

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

Recommended rule Ready

Verdict

add_script_export Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_script_export": {
      "limits": [
        {
          "counter": "add_script_export_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 add_script_export

What does the add_script_export tool do? +

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.

What parameters does add_script_export accept? +

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.

How do I enforce a policy on add_script_export? +

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.

What risk level is add_script_export? +

add_script_export is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_script_export? +

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.

How do I block add_script_export completely? +

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.

What MCP server provides add_script_export? +

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.