This record as markdown: /tools/keeveeg-godot-mcp/delete-shader.md
What delete_shader does on Godot
AI agents call delete_shader to permanently remove resources in Godot, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Shader file path to delete (e.g. res://shaders/my_shader.gdshader) |
Parameters from the server's own tool schema.
Why delete_shader is rated Critical
The tool permanently removes shader files from a Godot project without the ability to undo through the tool itself. Shader files are critical project assets whose deletion cannot be reversed by the tool's API, making this a destructive operation.
From the tool's definition Tool name is 'delete_shader' and description states 'Delete a shader file from the project'. This directly performs an irreversible deletion operation on project files.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs delete_shader 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 delete_shader, this is the rule to start with:
delete_shader is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Godot, apply this rule, and every delete_shader call is checked against it from then on.
Questions about delete_shader
Delete a shader file from the project. It is categorised as a Destructive tool in the Godot MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_shader accepts 1 parameter: path. Required: 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 delete_shader: 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.
delete_shader 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_shader 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_shader. 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_shader 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.
Across the catalogue