Modify a template with changes, optionally saving.
AI agents use modify_template to create or update resources in BlenderMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your BlenderMCP environment.
This tool creates or modifies data (a template) reversibly. Modifications can be undone by reverting to a previous template version or using other template management tools. It does not irreversibly destroy data (would be Destructive), execute arbitrary code (would be Execute), or create financial obligations.
From the tool's definition Tool name 'modify_template' combined with description 'Modify a template with changes, optionally saving' directly indicates data modification. The optional saving mechanism suggests the changes can be persisted to stored template data.
Attacks that exploit this kind of access
Modify a template with changes, optionally saving. It is categorised as a Write tool in the BlenderMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Blender MCP server in PolicyLayer and add a rule for modify_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.
modify_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 modify_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 modify_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.
modify_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 →