This record as markdown: /tools/yanhuifair-godot-mcp/create-shader-include.md
What create_shader_include does on Godot
AI agents use create_shader_include to create or update resources in Godot, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Godot environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | Output path (e.g. "shaders/common.gdshaderinc") |
Parameters from the server's own tool schema.
Why create_shader_include is rated Medium
The tool creates a new shader include file (.gdshaderinc), which is a reversible write operation that adds data to the project. It does not delete, execute arbitrary code, or trigger financial transactions. However, it has medium severity because malicious shader includes could affect game rendering behavior or be used to inject unwanted visual effects into a project.
From the tool's definition Tool name 'create_shader_include' and description 'Create a .gdshaderinc file' indicate file creation, which is a write operation that modifies the project filesystem by adding new resources.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs create_shader_include 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 create_shader_include, this is the rule to start with:
create_shader_include 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 Godot, apply this rule, and every create_shader_include call is checked against it from then on.
Questions about create_shader_include
Create a .gdshaderinc file. It is categorised as a Write tool in the Godot MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_shader_include 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 create_shader_include: 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.
create_shader_include 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 create_shader_include 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 create_shader_include. 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.
create_shader_include is provided by the Godot MCP server (@yanhuifair/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.
This server
Across the catalogue