Attach a GDScript to a node in a scene, or detach the current script.
AI agents use set_scene_script to create or update resources in Godot Mcp Pilot — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Mcp Pilot environment.
This tool creates or modifies scene configurations by attaching/detaching scripts, which are reversible changes to project data. While it does affect code execution indirectly (by binding executable scripts to nodes), the tool itself performs data modification rather than direct code execution.
From the tool's definition Tool description states it can 'Attach a GDScript to a node in a scene, or detach the current script' — this modifies scene structure and behavior by adding or removing executable code bindings.
Attacks that exploit this kind of access
Attach a GDScript to a node in a scene, or detach the current script. It is categorised as a Write tool in the Godot Mcp Pilot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Mcp Pilot MCP server in PolicyLayer and add a rule for set_scene_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 Mcp Pilot. Nothing to install.
set_scene_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 set_scene_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 set_scene_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.
set_scene_script is provided by the Godot Mcp Pilot MCP server (pushks18/godot-mcp-pilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →