Create a new Amplify shader from a predefined template (surface, unlit, urp_lit, transparent, post_process). The shader file is created and can then be opened in ASE.
AI agents use unity_amplify_create_from_template to create or update resources in Unity MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Unity MCP Server environment.
This tool creates new shader files in a Unity project, which is a reversible write operation. It doesn't execute arbitrary code or delete data, but it does modify the project structure by adding new assets. The severity is medium because while shader creation is generally safe and reversible, it could impact project state and any AI misuse (e.g., creating many unnecessary shaders) would have moderate blast radius.
From the tool's definition Tool description states: 'Create a new Amplify shader from a predefined template' and 'The shader file is created' — these are clear create/write operations that modify the project state by adding new files.
Documented attack patterns abuse exactly the kind of access unity_amplify_create_from_template gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Unity MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for unity_amplify_create_from_template:
{
"version": "1",
"default": "deny",
"tools": {
"unity_amplify_create_from_template": {
"limits": [
{
"counter": "unity_amplify_create_from_template_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}unity_amplify_create_from_template 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 a new Amplify shader from a predefined template (surface, unlit, urp_lit, transparent, post_process). The shader file is created and can then be opened in ASE. It is categorised as a Write tool in the Unity MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Unity MCP Server MCP server in PolicyLayer and add a rule for unity_amplify_create_from_template: 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 Unity MCP Server. Nothing to install.
unity_amplify_create_from_template 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 unity_amplify_create_from_template 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 unity_amplify_create_from_template. 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.
unity_amplify_create_from_template is provided by the Unity MCP Server MCP server (anklebreaker-studio/unity-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 324 Unity MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
324 Unity MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.