AI agents use update_roof to create or update resources in IFC Bonsai MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IFC Bonsai MCP environment.
The tool modifies IFC architectural model data (roofs are structural elements). While the description is empty (lowering confidence slightly), the tool name and sibling tools in an IFC creation/editing context indicate this creates or modifies model state reversibly. It is not Destructive because update typically implies modification rather than deletion, and there is no evidence of irreversible operations.
From the tool's definition Tool name 'update_roof' and context of sibling tools (create_door, create_slab, create_roof, create_mesh_ifc) indicate modification of IFC model geometry; description is empty but naming pattern and server purpose (create and edit IFC models) strongly suggest…
Documented attack patterns abuse exactly the kind of access update_roof 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 update_roof:
{
"version": "1",
"default": "deny",
"tools": {
"update_roof": {
"limits": [
{
"counter": "update_roof_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_roof stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
update_roof. It is categorised as a Write tool in the IFC Bonsai MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IFC Bonsai MCP server in PolicyLayer and add a rule for update_roof: 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.
update_roof is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_roof 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 update_roof. 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.
update_roof 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.
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.