AI agents use update_door 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 existing door objects in an IFC model, which is a reversible write operation. It does not delete (Destructive), execute arbitrary code (Execute), or move money (Financial). While the empty description reduces confidence, the naming convention and server context—focused on 'create and edit IFC models'—clearly positions this as a Write-class tool.
From the tool's definition Tool name 'update_door' and context within IFC Bonsai MCP server that creates and edits IFC models. Sibling tools include create_door, create_mesh_ifc, and create_slab, establishing a pattern of Write operations. Tool description is empty, limiting precision.
Documented attack patterns abuse exactly the kind of access update_door 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_door:
{
"version": "1",
"default": "deny",
"tools": {
"update_door": {
"limits": [
{
"counter": "update_door_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_door 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_door. 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_door: 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_door 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_door 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_door. 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_door 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.