cao_valider_ifc
WHEN you need to check an IFC scene without a buildingSMART account. Same scene as cao_generer_ifc. Returns {ok, schema_ifc4, regles, problemes}: IFC4 schema + EXPRESS rules, millimetre units, material layers on every IfcWall, named IfcSpace, thermal conductivity in Pset_MaterialThermal, every el...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-valider-ifc.md
What cao_valider_ifc does on Immobilier
AI agents use cao_valider_ifc to create or update resources in Immobilier, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Immobilier environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
murs | array | — | Walls: plan segments extruded vertically. Every coordinate in this whole scene is in MILLIMETRES, in a single plan frame whose origin you choose — X to the righ |
plan | array | — | 2D reference lines — drawn flat, never extruded and never counted in the quantities. Use them for axes, plot limits or setting-out marks. |
boites | array | — | Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[]. |
georef | object | — | Optional Lambert-93 (EPSG:2154) false origin for IfcMapConversion. Local millimetres are scaled by 0.001 to CRS metres. Do not invent coordinates: omit est/nord |
cercles | array | — | Circles on the 2D plan, alongside plan[] lines: each has a centre and a radius, in the same unit as the plan. Use for round shapes a polyline would render badly |
reseaux | array | — | Plumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type). |
toitures | array | — | Roofs — used only by cao_pdf. WITHOUT this field: a flat roof is auto-generated over the footprint of ALL walls (legacy default). WITH it: compose freely — each |
plomberie | array | — | Sanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite. |
decoration | array | — | Paint/finish per wall — used only by cao_pdf. Colors the elevations (exterior face) and the axonometric view (face auto-detected by orientation relative to the |
ouvertures | array | — | Doors/windows embedded in a wall — used only by cao_pdf (elevations + axonometric view), no effect on dxf/metres. |
electricite | array | — | Electrical symbols (outlets, switches, lights…) — used only by cao_pdf (dedicated technical plan + quantities), no effect on dxf/metres/render. Position: attach |
compositions | object | — | Named wall/slab layer sets declared by the project. A key that matches an inferred kind (mur_exterieur, refend, cloison, plancher, toiture) or murs[].compositio |
Parameters from the server's own tool schema.
Why cao_valider_ifc is rated Medium
An AI agent can call cao_valider_ifc faster than any human can review: one bad instruction and it creates or modifies resources in Immobilier by the hundred, each call as confident as the last.
Risk signalsHigh parameter count (94 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_valider_ifc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Immobilier, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cao_valider_ifc, this is the rule to start with:
cao_valider_ifc 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Immobilier, apply this rule, and every cao_valider_ifc call is checked against it from then on.
Questions about cao_valider_ifc
WHEN you need to check an IFC scene without a buildingSMART account. Same scene as cao_generer_ifc. Returns {ok, schema_ifc4, regles, problemes}: IFC4 schema + EXPRESS rules, millimetre units, material layers on every IfcWall, named IfcSpace, thermal conductivity in Pset_MaterialThermal, every element in a storey. It is categorised as a Write tool in the Immobilier MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
cao_valider_ifc accepts 12 parameters: murs, plan, boites, georef, cercles, reseaux, toitures, plomberie, decoration, ouvertures, electricite, compositions. The full parameter table on this page comes from the server's own tool schema.
Register the Immobilier MCP server in PolicyLayer and add a rule for cao_valider_ifc: 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 Immobilier. Nothing to install.
cao_valider_ifc 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 cao_valider_ifc 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 cao_valider_ifc. 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.
cao_valider_ifc is provided by the Immobilier MCP server (https://synergieloc.fr/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Immobilier, and thousands of servers like it.
This server
Across the catalogue