This record as markdown: /tools/kiln/set-material.md
What set_material does on Kiln
AI agents use set_material to create or update resources in Kiln, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kiln environment.
Why set_material is rated Medium
This tool modifies printer state by changing the active material for printing jobs. It is reversible (material can be changed again) and has side effects limited to future print jobs, making it a Write operation. Severity is medium because incorrect material selection could result in failed prints or wasted materials, but does not cause permanent damage.
From the tool's definition Tool name 'set_material' on a 3D printer control server (Kiln) in the context of spool management ('add_spool' is a sibling tool). The name indicates modification of printer material configuration.
Attacks that exploit this kind of access
The rule that runs set_material 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 set_material, this is the rule to start with:
set_material stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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 set_material call is checked against it from then on.
Questions about set_material
set_material is a write tool on the Kiln MCP server. It is categorised as a Write tool in the Kiln MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kiln MCP server in PolicyLayer and add a rule for set_material: 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.
set_material is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_material 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 set_material. 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.
set_material 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