This record as markdown: /tools/kiln/split-mesh-by-component.md
What split_mesh_by_component does on Kiln
AI agents invoke split_mesh_by_component 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 split_mesh_by_component is rated High
Based on the name alone, this tool likely performs a mesh splitting operation on 3D model geometry, which is an execute/write-level operation modifying in-memory or file-based mesh data. The context of sibling tools (add_mesh_chamfer, add_mesh_fillet, add_assembly_part) confirms this server manipulates 3D geometry.
From the tool's definition Tool name: 'split_mesh_by_component'; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs split_mesh_by_component 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 split_mesh_by_component, this is the rule to start with:
split_mesh_by_component 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 split_mesh_by_component call is checked against it from then on.
Questions about split_mesh_by_component
split_mesh_by_component 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 split_mesh_by_component: 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.
split_mesh_by_component 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 split_mesh_by_component 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 split_mesh_by_component. 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.
split_mesh_by_component 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