This record as markdown: /tools/kiln/get-design-version.md
What get_design_version does on Kiln
AI agents call get_design_version 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.
Why get_design_version is rated Low
The tool name indicates a query/retrieval operation ('get') of design versioning information, consistent with Read operations. With no description provided, confidence is moderate. The context (3D printer control) suggests this likely retrieves non-sensitive metadata about design versions rather than executing operations or modifying state. Severity is low as version queries pose minimal risk even if misused.
From the tool's definition Tool name 'get_design_version' suggests retrieval of version metadata; description is empty, limiting certainty.
Attacks that exploit this kind of access
The rule that runs get_design_version 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 get_design_version, this is the rule to start with:
get_design_version is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Kiln, apply this rule, and every get_design_version call is checked against it from then on.
Questions about get_design_version
get_design_version 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.
Register the Kiln MCP server in PolicyLayer and add a rule for get_design_version: 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.
get_design_version 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 get_design_version 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 get_design_version. 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.
get_design_version 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.
More on Kiln, and thousands of servers like it.
This server
Across the catalogue