shader_create
Create a Shader resource with optional initial code and save it as a .gdshader file. DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/shader-create.md
What shader_create does on Breakpoint
AI agents use shader_create to create or update resources in Breakpoint, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Breakpoint environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | — | Initial GDShader source (e.g. "shader_type canvas_item; ...") |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
to_path | string | Yes | Destination res:// path, e.g. res://shaders/glow.gdshader |
Parameters from the server's own tool schema.
Why shader_create is rated Medium
While the description uses the word 'DESTRUCTIVE', the actual operation is creating/writing a new file, not overwriting or irreversibly deleting existing data. The confirmation gate further reduces risk. This is a Write operation (creates data reversibly) rather than Destructive.
From the tool's definition Tool description explicitly states 'writes a file' and creates a Shader resource, saving it as a .gdshader file. The description mentions 'gated by confirmation' which mitigates the destructive aspect by requiring user approval before execution.
Risk signalsAccepts freeform code/query input (code)
Attacks that exploit this kind of access
The rule that runs shader_create safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Breakpoint, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For shader_create, this is the rule to start with:
shader_create 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Breakpoint, apply this rule, and every shader_create call is checked against it from then on.
Questions about shader_create
Create a Shader resource with optional initial code and save it as a .gdshader file. DESTRUCTIVE (writes a file) — gated by confirmation. It is categorised as a Write tool in the Breakpoint MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
shader_create accepts 3 parameters: code, confirm, to_path. Required: to_path. The full parameter table on this page comes from the server's own tool schema.
Register the Breakpoint MCP server in PolicyLayer and add a rule for shader_create: 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 Breakpoint. Nothing to install.
shader_create 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_create 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_create. 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_create is provided by the Breakpoint MCP server (breakpoint-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Breakpoint, and thousands of servers like it.
This server
Across the catalogue