editor_attach_script · Godot MCP: Risk & Policy

WHAT IT DOES

What editor_attach_script does on Godot

AI agents use editor_attach_script 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	Node path
`script`	string	Yes	Script path to attach

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why editor_attach_script needs a policy

Attaching a script to a node is a Write operation: it creates or modifies project data (the node–script binding) reversibly. While this is a development-oriented action within the Godot editor rather than a destructive delete or an Execute that runs arbitrary code, it does permanently alter the project's composition.

From the tool's definition Attach a script to a node in the editor — this modifies the node's script property, creating a persistent change to the scene/project structure.

Risk signalsAccepts freeform code/query input (script) · Accepts file system path (path)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

editor_attach_script Rate-limited

editor_attach_script 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": {
    "editor_attach_script": {
      "limits": [
        {
          "counter": "editor_attach_script_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 editor_attach_script

What does the editor_attach_script tool do? +

Attach a script to a node in the editor. 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 editor_attach_script accept? +

editor_attach_script accepts 2 parameters: path, script. Required: path, script. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on editor_attach_script? +

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

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

Can I rate-limit editor_attach_script? +

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

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

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