This record as markdown: /tools/kiln/merge-stl.md
What merge_stl does on Kiln
AI agents use merge_stl 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 merge_stl is rated Medium
The name implies merging STL (3D model) files, which is a write/modification operation on model data. Without a description, confidence is reduced. Merging files is reversible (original files may still exist), so Write is most appropriate. Not classified as Execute since no code execution or printer command is implied by the name alone.
From the tool's definition Tool name 'merge_stl' suggests combining STL files; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs merge_stl 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 merge_stl, this is the rule to start with:
merge_stl 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 merge_stl call is checked against it from then on.
Questions about merge_stl
merge_stl 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 merge_stl: 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.
merge_stl 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 merge_stl 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 merge_stl. 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.
merge_stl 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