list_design_versions

A read tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/list-design-versions.md

WHAT IT DOES

What list_design_versions does on Kiln

AI agents call list_design_versions to retrieve information from Kiln without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_design_versions is rated Low

The tool name strongly suggests listing/retrieving design versions in a 3D printer control context. This is a non-destructive query operation with no side effects. The empty description reduces confidence slightly, but the naming convention and context (sibling tools involve explicit Write/Execute/Destructive actions like add_*, activate_*, ams_status) confirm this is a read-only operation.

From the tool's definition Tool name 'list_design_versions' indicates a retrieval operation that queries available design versions without modification. The 'list' prefix is characteristic of Read operations (e.g., list, get, fetch).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_design_versions safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Kiln, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_design_versions, this is the rule to start with:

list_design_versions Allowed

list_design_versions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_design_versions": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every list_design_versions call is checked against it from then on.

FAQ

Questions about list_design_versions

What does the list_design_versions tool do? +

list_design_versions is a read tool on the Kiln MCP server. It is categorised as a Read tool in the Kiln MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_design_versions? +

Register the Kiln MCP server in PolicyLayer and add a rule for list_design_versions: 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.

What risk level is list_design_versions? +

list_design_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_design_versions? +

Yes. Add a rate_limit block to the list_design_versions 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.

How do I block list_design_versions completely? +

Set action: deny in the PolicyLayer policy for list_design_versions. 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.

What MCP server provides list_design_versions? +

list_design_versions 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.

KEEP EXPLORING

More on Kiln, and thousands of servers like it.

This server

All 402 Kiln tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →