This record as markdown: /tools/keeveeg-godot-mcp/attach-script.md
What attach_script does on Godot
AI agents use 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 |
|---|---|---|---|
node_path | string | Yes | Node to attach script to (e.g. 'Player' or '' for scene root) |
script_path | string | Yes | Script file path to attach |
Parameters from the server's own tool schema.
Why attach_script is rated Medium
This tool modifies scene configuration by adding executable code to a node. While it enables code execution, the tool itself performs a write/attachment operation rather than directly executing code—the execution happens later when the scene runs. The severity is high because attached scripts can perform arbitrary operations, but the tool's direct action is to modify scene data, making it Write category.
From the tool's definition Tool attaches a GDScript to a node. GDScript is Godot's scripting language. Attaching a script to a node modifies the scene structure and node behavior, creating new executable code that will run when the scene executes.
Attacks that exploit this kind of access
The rule that runs 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 attach_script, this is the rule to start with:
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 attach_script call is checked against it from then on.
Questions about attach_script
Attach a GDScript to a node in the scene. 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.
attach_script accepts 2 parameters: node_path, script_path. Required: node_path, script_path. 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 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.
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 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 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.
attach_script is provided by the Godot MCP server (@keeveeg/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