cao_nomenclatures
WHEN someone needs the SCHEDULES of a house design, as Revit calls them: the door and window schedule (one mark per type, P1 for doors and F1 for windows, with size, sill height, leaves, clear opening width, accessibility and the count per storey, then every opening with the rooms on each side), ...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-nomenclatures.md
What cao_nomenclatures does on Immobilier
AI agents call cao_nomenclatures to permanently remove resources in Immobilier, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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_nomenclatures is rated Critical
An AI agent that decides to call cao_nomenclatures doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Immobilier is gone. There is no undo for destructive operations.
Risk signalsHigh parameter count (94 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_nomenclatures 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_nomenclatures, this is the rule to start with:
cao_nomenclatures is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Immobilier, apply this rule, and every cao_nomenclatures call is checked against it from then on.
Questions about cao_nomenclatures
WHEN someone needs the SCHEDULES of a house design, as Revit calls them: the door and window schedule (one mark per type, P1 for doors and F1 for windows, with size, sill height, leaves, clear opening width, accessibility and the count per storey, then every opening with the rooms on each side), the room schedule (floor, habitable and Carrez areas, perimeter, ceiling height and volume, with totals per storey and for the building) and the equipment schedule (sanitary, electrical, heating, ventilation and furniture counts per storey). The figures match the IFC export exactly: same spaces, same door and window types, same IsExternal flag. It is categorised as a Destructive tool in the Immobilier MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
cao_nomenclatures 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_nomenclatures: 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_nomenclatures is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the cao_nomenclatures 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_nomenclatures. 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_nomenclatures 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.
Across the catalogue