Run a GDScript snippet headlessly inside a project and return the output.
AI agents invoke run_gdscript to trigger actions in Godot Mcp Pilot. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool permits execution of arbitrary code within the Godot runtime environment. An AI agent misusing this could read/write files, modify game state, execute system calls via Godot's OS API, or trigger destructive operations on the project.
From the tool's definition run_gdscript runs arbitrary GDScript code ('Run a GDScript snippet headlessly') in the context of a Godot project. GDScript has full access to the Godot engine API, filesystem operations, and project state.
Attacks that exploit this kind of access
Run a GDScript snippet headlessly inside a project and return the output. It is categorised as a Execute tool in the Godot Mcp Pilot MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Godot Mcp Pilot MCP server in PolicyLayer and add a rule for run_gdscript: 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.
run_gdscript is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_gdscript 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 run_gdscript. 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.
run_gdscript 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 →