Delete an FDS mesh by its ID.
AI agents call bulc_delete_mesh to permanently remove resources in BULC Building Designer — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs an irreversible deletion operation on simulation mesh data. Once deleted, the mesh cannot be recovered through normal means. In the context of building design and fire simulation, deleting a mesh removes structural geometry that affects simulation accuracy and design integrity.
From the tool's definition Tool name explicitly states 'delete' and description confirms 'Delete an FDS mesh by its ID.' The action is irreversible and removes data from the simulation model.
Attacks that exploit this kind of access
Delete an FDS mesh by its ID. It is categorised as a Destructive tool in the BULC Building Designer MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BULC Building Designer MCP server in PolicyLayer and add a rule for bulc_delete_mesh: 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 BULC Building Designer. Nothing to install.
bulc_delete_mesh 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 bulc_delete_mesh 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 bulc_delete_mesh. 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.
bulc_delete_mesh is provided by the BULC Building Designer MCP server (using76/bulc_mcp). 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 →