Create, read, inspect, and configure ShaderMaterial parameters
AI agents use shader to create or update resources in Godot Devtool — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot Devtool environment.
The tool permits creating and configuring shader materials, which are reversible modifications to a Godot project's graphics state. While it does not delete or execute arbitrary code, it modifies material properties that affect rendering.
From the tool's definition Tool description states 'Create, read, inspect, and configure ShaderMaterial parameters' — the 'create' and 'configure' verbs indicate modification capabilities beyond read-only access.
Documented attack patterns abuse exactly the kind of access shader gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Godot Devtool, and nothing reaches the server without passing your rules. This is the rule we recommend for shader:
{
"version": "1",
"default": "deny",
"tools": {
"shader": {
"limits": [
{
"counter": "shader_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}shader stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create, read, inspect, and configure ShaderMaterial parameters. It is categorised as a Write tool in the Godot Devtool MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Godot Devtool MCP server in PolicyLayer and add a rule for 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 Devtool. Nothing to install.
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 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 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.
shader is provided by the Godot Devtool MCP server (wangdiandao/godot-devtool). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 101 Godot Devtool tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
101 Godot Devtool tools catalogued and risk-classified — across an index of 42,500+ MCP servers.