cao_ids_verifier
WHEN a BIM manager's information requirements (an IDS 1.0 file, buildingSMART) must be checked on a model before delivery — ours built from the scene, or an architect's IFC: checks every specification (entity, attribute, property compared in SI units, classification, material, partOf; required, o...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-ids-verifier.md
What cao_ids_verifier does on Immobilier
AI agents call cao_ids_verifier to retrieve information from Immobilier without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
bcf | boolean | — | True to add the failures as a BCF 2.1 zip in base64 (bcf_base64). |
ids | string | — | Optional IDS 1.0 XML text; default: our French housing IDS. |
ifc | string | — | Optional IFC text (STEP) to check instead of the scene; an architect's model keeps its GlobalIds. |
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 |
Parameters from the server's own tool schema.
Why cao_ids_verifier is rated Low
Even though cao_ids_verifier only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHigh parameter count (97 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_ids_verifier 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_ids_verifier, this is the rule to start with:
cao_ids_verifier is read-only, so it stays allowed. 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_ids_verifier call is checked against it from then on.
Questions about cao_ids_verifier
WHEN a BIM manager's information requirements (an IDS 1.0 file, buildingSMART) must be checked on a model before delivery — ours built from the scene, or an architect's IFC: checks every specification (entity, attribute, property compared in SI units, classification, material, partOf; required, optional, prohibited; target IFC version) and returns, per specification, the applicable elements and those failing with their reasons; bcf: true adds the failures as BCF 2.1 topics with their objects. Without ids, checks our French housing IDS (rooms with net, habitable and Carrez areas, typed doors and windows, accessibility, load-bearing walls with materials, storeys, stairs, Lambert-93), free at GET /api/v1/cao/ifc/ids/logement-fr. It is categorised as a Read tool in the Immobilier MCP Server, which means it retrieves data without modifying state.
cao_ids_verifier accepts 12 parameters: bcf, ids, ifc, murs, plan, boites, georef, cercles, reseaux, toitures, plomberie, decoration. 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_ids_verifier: 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_ids_verifier is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cao_ids_verifier 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_ids_verifier. 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_ids_verifier 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