Delete a GDScript (.gd) file from the project
AI agents call delete_script to permanently remove resources in Godot MCP Unified — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting script files is a destructive operation that cannot be undone through normal MCP tool calls. The blast radius is high because loss of source code can break game functionality, damage project integrity, and require version control recovery. This is more severe than Write (reversible modifications) but not Financial, so Destructive is the appropriate category.
From the tool's definition Tool name is 'delete_script' and description states 'Delete a GDScript (.gd) file from the project' — the verb 'delete' combined with file removal is irreversible data destruction.
Attacks that exploit this kind of access
Delete a GDScript (.gd) file from the project. It is categorised as a Destructive tool in the Godot MCP Unified MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Godot MCP Unified MCP server in PolicyLayer and add a rule for delete_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 Unified. Nothing to install.
delete_script is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_script is provided by the Godot MCP Unified MCP server (pierrealexandreguillemin-a11y/godot-mcp-unified). 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 →