shader_set_code
Replace the source code of an existing .gdshader resource and save it. DESTRUCTIVE (writes a file) — gated by confirmation.
This record as markdown: /tools/breakpoint-mcp/shader-set-code.md
What shader_set_code does on Breakpoint
AI agents call shader_set_code to permanently remove resources in Breakpoint, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | string | Yes | New GDShader source |
path | string | Yes | Shader res:// path |
confirm | boolean | — | Auto-approve this destructive action (skip the confirmation prompt) |
Parameters from the server's own tool schema.
Why shader_set_code is rated Critical
The tool explicitly overwrites existing shader source code and saves it to disk, which is an irreversible file modification. The description itself labels this as DESTRUCTIVE. While a confirmation gate exists, the action of replacing file contents cannot be undone without a backup, making this Destructive rather than merely Write.
From the tool's definition Replace the source code of an existing .gdshader resource and save it. DESTRUCTIVE (writes a file) — gated by confirmation.
Risk signalsAccepts freeform code/query input (code) · Accepts file system path (path)
Attacks that exploit this kind of access
The rule that runs shader_set_code 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_set_code, this is the rule to start with:
shader_set_code 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 Breakpoint, apply this rule, and every shader_set_code call is checked against it from then on.
Questions about shader_set_code
Replace the source code of an existing .gdshader resource and save it. DESTRUCTIVE (writes a file) — gated by confirmation. It is categorised as a Destructive tool in the Breakpoint MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
shader_set_code accepts 3 parameters: code, path, confirm. Required: code, 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_set_code: 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_set_code 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 shader_set_code 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_set_code. 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_set_code 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.
Across the catalogue