editor_attach_script
Attach a script to a node in the editor.
This record as markdown: /tools/yanhuifair-godot-mcp/editor-attach-script.md
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.
| 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 editor_attach_script is rated Medium
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
The rule that runs editor_attach_script 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 editor_attach_script, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every editor_attach_script call is checked against it from then on.
Questions about editor_attach_script
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.
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.
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.
editor_attach_script 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 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.
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.
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.
More on Godot, and thousands of servers like it.
This server
Across the catalogue