This record as markdown: /tools/kiln/slice-and-estimate.md
What slice_and_estimate does on Kiln
AI agents invoke slice_and_estimate to trigger actions in Kiln. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why slice_and_estimate is rated High
Slicing a 3D model involves executing a slicer program against a model file to generate G-code or similar output. This is an Execute-category action as it triggers external computation and potentially writes output files. The description is empty, which lowers confidence, but the name strongly implies execution of a slicing pipeline.
From the tool's definition Tool name 'slice_and_estimate' implies running a slicing operation (computationally intensive execution) and cost/time estimation on a 3D model, likely triggering external slicer processes.
Attacks that exploit this kind of access
The rule that runs slice_and_estimate 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 slice_and_estimate, this is the rule to start with:
slice_and_estimate stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 slice_and_estimate call is checked against it from then on.
Questions about slice_and_estimate
slice_and_estimate is a execute tool on the Kiln MCP server. It is categorised as a Execute tool in the Kiln MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Kiln MCP server in PolicyLayer and add a rule for slice_and_estimate: 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.
slice_and_estimate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the slice_and_estimate 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 slice_and_estimate. 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.
slice_and_estimate 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