remove_mesh_floating_regions
AI agents call remove_mesh_floating_regions to permanently remove resources in Kiln — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The word 'remove' combined with 'mesh_floating_regions' strongly suggests this tool deletes disconnected portions of a 3D mesh geometry, which is typically an irreversible destructive operation. However, the empty description lowers confidence — it could potentially be a non-destructive operation that marks or isolates regions.
From the tool's definition Tool name 'remove_mesh_floating_regions' implies irreversible deletion of mesh geometry (floating/disconnected regions). Description is empty, lowering confidence.
Attacks that exploit this kind of access
remove_mesh_floating_regions. It is categorised as a Destructive tool in the Kiln MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Kiln MCP server in PolicyLayer and add a rule for remove_mesh_floating_regions: 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.
remove_mesh_floating_regions is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_mesh_floating_regions 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 remove_mesh_floating_regions. 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.
remove_mesh_floating_regions 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →