bim_create_wall
AI agents use bim_create_wall 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 (writes) a new wall object in a FreeCAD BIM model. It is reversible — walls can be deleted or modified after creation. It does not execute arbitrary code, delete data irreversibly, or commit financial transactions. The primary risk is misuse by an AI agent to create unwanted or structurally invalid walls in a design, requiring human review/correction.
From the tool's definition Tool name is 'bim_create_wall' — the verb 'create' indicates it adds new data to a CAD model. This is a Building Information Modeling (BIM) operation that mirrors sibling tools like bim_create_column, bim_create_door, bim_create_roof, bim_create_slab, and…
Attacks that exploit this kind of access
bim_create_wall. 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_wall: 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_wall 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_wall 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_wall. 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_wall 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 →