slice_and_estimate · Kiln MCP: Risk & Policy

WHAT IT DOES

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 IT NEEDS A POLICY

Why slice_and_estimate needs a policy

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

Recommended rule Ready

Verdict

slice_and_estimate Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "slice_and_estimate": {
      "limits": [
        {
          "counter": "slice_and_estimate_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Kiln, so you can run agents against it safely.

FAQ

Questions about slice_and_estimate

What does the slice_and_estimate tool do? +

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

How do I enforce a policy on slice_and_estimate? +

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.

What risk level is slice_and_estimate? +

slice_and_estimate is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit slice_and_estimate? +

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.

How do I block slice_and_estimate completely? +

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.

What MCP server provides slice_and_estimate? +

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.