bim_create_door
AI agents use bim_create_door to create or update resources in FreeCAD MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FreeCAD MCP environment.
This tool creates BIM (Building Information Model) objects—specifically door elements in a CAD design. Creation is a reversible Write operation (the door can be deleted or modified). Severity is medium because misuse could corrupt a design project or create unwanted architectural elements, but effects are limited to the CAD model scope and don't involve destructive data loss, code execution, or financial impact.
From the tool's definition Tool name 'bim_create_door' and sibling tools (bim_create_column, bim_create_roof, bim_create_slab, bim_create_wall, bim_create_window) all follow the 'create' pattern, indicating data creation operations.
Attacks that exploit this kind of access
bim_create_door. It is categorised as a Write tool in the FreeCAD MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FreeCAD MCP server in PolicyLayer and add a rule for bim_create_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 FreeCAD MCP. Nothing to install.
bim_create_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 bim_create_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 bim_create_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.
bim_create_door is provided by the FreeCAD MCP server (sandraschi/freecad-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 →