Critical Risk →

remove_style

remove_style

How to control remove_style ↓

AI agents call remove_style to permanently remove resources in IFC Bonsai MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

The 'remove' prefix typically indicates deletion/destruction of data. Given the context of an IFC model editor with style-related tools (apply_style_to_object, create_pbr_style), this tool likely permanently removes a style definition, which may be irreversible. Confidence is moderate because the description is empty and the exact behavior is inferred from naming conventions and sibling tools.

From the tool's definition Tool name 'remove_style' alongside sibling tools like 'apply_style_to_object' and 'create_pbr_style' suggests it irreversibly removes a style from the IFC model.

Documented attack patterns abuse exactly the kind of access remove_style gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and IFC Bonsai MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_style:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "remove_style"
  ]
}

remove_style disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register IFC Bonsai MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the remove_style tool do? +

remove_style. It is categorised as a Destructive tool in the IFC Bonsai MCP 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_style? +

Register the IFC Bonsai MCP server in PolicyLayer and add a rule for remove_style: 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 IFC Bonsai MCP. Nothing to install.

What risk level is remove_style? +

remove_style 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_style? +

Yes. Add a rate_limit block to the remove_style 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_style completely? +

Set action: deny in the PolicyLayer policy for remove_style. 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_style? +

remove_style is provided by the IFC Bonsai MCP server (show2instruct/ifc-bonsai-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every IFC Bonsai MCP tool call.

Deterministic rules across all 52 IFC Bonsai MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

52 IFC Bonsai MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.