Overwrite the GLSL code of an existing shader file.
AI agents use edit_shader to create or update resources in Godot MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot MCP Server environment.
This tool creates or modifies shader code reversibly. While not destructive (the original can be recovered from version control or backups), overwriting shader files affects game rendering and visual behavior. High severity reflects that corrupted shaders can break game appearance/performance, but the operation remains reversible unlike Destructive category.
From the tool's definition Tool description explicitly states 'Overwrite the GLSL code of an existing shader file' — modifying file content is a Write operation. Sibling tools like add_node, add_animation_track confirm this server manages game asset creation/modification.
Attacks that exploit this kind of access
Overwrite the GLSL code of an existing shader file. It is categorised as a Write tool in the Godot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot MCP Server MCP server in PolicyLayer and add a rule for edit_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 MCP Server. Nothing to install.
edit_shader 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 edit_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 edit_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.
edit_shader is provided by the Godot MCP Server MCP server (neondeex/godotmcp-pro-free-client). 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 →