AI agents call list_design_templates to retrieve information from Kiln without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to list or retrieve design templates, which is a read-only operation with no side effects. The 'list_' prefix is characteristic of Read category tools. Despite the empty description reducing confidence slightly, the tool name provides sufficient evidence for classification as a Read operation with low severity, as it only retrieves information about available templates without creating, modifying,…
From the tool's definition Tool name 'list_design_templates' indicates retrieval of template data; no description provided but naming convention and context (3D printer control server) suggest querying available design templates without modification.
Attacks that exploit this kind of access
list_design_templates. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.
Register the Kiln MCP server in PolicyLayer and add a rule for list_design_templates: 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 Kiln. Nothing to install.
list_design_templates 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 list_design_templates 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 list_design_templates. 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.
list_design_templates is provided by the Kiln MCP server (codeofaxel/Kiln). 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 →