List built-in whiteboard templates/components that can be inserted with template_insert. Templates are lightweight annotate_batch recipes intended for reusable architecture parts.
AI agents call template_list to retrieve information from Whiteboard without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves template metadata for display purposes. It has no side effects, makes no modifications to the canvas or data, and does not execute code or trigger external operations. The tool simply enumerates pre-built templates available for potential future use via template_insert. Misuse would have negligible impact as the worst case is viewing template information.
From the tool's definition Tool description states 'List built-in whiteboard templates/components' - the primary function is to retrieve and display a list of available templates. No creation, modification, deletion, or execution of external code occurs.
Attacks that exploit this kind of access
List built-in whiteboard templates/components that can be inserted with template_insert. Templates are lightweight annotate_batch recipes intended for reusable architecture parts. It is categorised as a Read tool in the Whiteboard MCP Server, which means it retrieves data without modifying state.
Register the Whiteboard MCP server in PolicyLayer and add a rule for template_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the template_list 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_list. 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_list 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 →