Apply the template named 'name', with optional overrides.
AI agents invoke apply_template to trigger actions in BlenderMCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Applying a template executes a set of predefined operations in Blender (scene setup, object creation, material assignment, etc.), which constitutes triggering external operations. It is more than a simple write since it runs a compound action. The 'optional overrides' suggest parameterized execution. Severity is medium because misuse could corrupt a Blender scene but is limited to the local Blender environment.
From the tool's definition 'Apply the template named name, with optional overrides' — applying a template triggers operations in Blender that modify the scene/state, with overrides potentially altering behavior
Attacks that exploit this kind of access
Apply the template named 'name', with optional overrides. It is categorised as a Execute tool in the BlenderMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Blender MCP server in PolicyLayer and add a rule for apply_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 BlenderMCP. Nothing to install.
apply_template is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the apply_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 apply_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.
apply_template is provided by the Blender MCP server (sk-dev-ai/blender-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →