This record as markdown: /tools/kiln/estimate-supports.md
What estimate_supports does on Kiln
AI agents call estimate_supports 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 estimate_supports is rated Low
The name suggests a computational analysis or retrieval of support structure data (common in 3D printing workflows), which implies a read-only operation. With no description provided, confidence is moderate. The tool does not appear to modify printer configuration, execute print jobs, or delete data based on naming conventions alone.
From the tool's definition Tool name 'estimate_supports' with empty description; inferred to retrieve or calculate support structure estimates for 3D printing without modifying printer state or executing operations.
Attacks that exploit this kind of access
The rule that runs estimate_supports 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 estimate_supports, this is the rule to start with:
estimate_supports 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 estimate_supports call is checked against it from then on.
Questions about estimate_supports
estimate_supports 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 estimate_supports: 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.
estimate_supports 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 estimate_supports 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 estimate_supports. 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.
estimate_supports 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