New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

remove_mesh_floating_regions

A destructive tool on the Kiln MCP server.

SERVERKiln SOURCEcodeofaxel/Kiln
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kiln/remove-mesh-floating-regions.md

What remove_mesh_floating_regions does on Kiln

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.

Why remove_mesh_floating_regions is rated Critical

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.

Questions about remove_mesh_floating_regions

What does the remove_mesh_floating_regions tool do? +

remove_mesh_floating_regions is a destructive tool on the Kiln MCP server. 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.

How do I enforce a policy on remove_mesh_floating_regions? +

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.

What risk level is remove_mesh_floating_regions? +

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.

Can I rate-limit remove_mesh_floating_regions? +

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.

How do I block remove_mesh_floating_regions completely? +

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.

What MCP server provides remove_mesh_floating_regions? +

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.

More on Kiln, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Kiln's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.