Insert a built-in or file-based template onto a canvas. Templates are resolved into annotate_batch annotations, so they remain editable after insertion. Use templateId for built-ins or templatePath for a custom JSON template.
AI agents use template_insert to create or update resources in Whiteboard — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Whiteboard environment.
This tool creates or modifies canvas content (drawings/annotations) in a reversible manner. While it adds elements to the canvas, these remain editable after insertion, making it a Write operation rather than Destructive. The blast radius is medium because malicious template injection could clutter or deface collaborative diagrams, but changes can be undone through normal editing operations.
From the tool's definition Tool description states it 'Insert[s] a built-in or file-based template onto a canvas' and that 'Templates are resolved into annotate_batch annotations', indicating creation/modification of canvas content.
Attacks that exploit this kind of access
Insert a built-in or file-based template onto a canvas. Templates are resolved into annotate_batch annotations, so they remain editable after insertion. Use templateId for built-ins or templatePath for a custom JSON template. It is categorised as a Write tool in the Whiteboard MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Whiteboard MCP server in PolicyLayer and add a rule for template_insert: 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 Whiteboard. Nothing to install.
template_insert 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 template_insert 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 template_insert. 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.
template_insert is provided by the Whiteboard MCP server (kamiazya/whiteboard). 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 →