This record as markdown: /tools/kiln/validate-assembly.md
What validate_assembly does on Kiln
AI agents call validate_assembly 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 validate_assembly is rated Low
The name 'validate_assembly' most naturally implies inspecting or checking assembly configuration/state without making changes, which aligns with Read category. However, confidence is lowered due to missing description and the ambiguity of 'validate' in 3D printing contexts—it could potentially trigger printer-side validation logic (Execute).
From the tool's definition Tool name 'validate_assembly' suggests a validation/checking operation with no modification verb. No description provided to clarify intent.
Attacks that exploit this kind of access
The rule that runs validate_assembly 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 validate_assembly, this is the rule to start with:
validate_assembly 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 validate_assembly call is checked against it from then on.
Questions about validate_assembly
validate_assembly 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 validate_assembly: 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.
validate_assembly 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 validate_assembly 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 validate_assembly. 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.
validate_assembly 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