cao_urbanisme
WHEN a design must be checked against the LOCAL PLANNING RULES of its zone (French PLU) before a building-permit application. Measures on the CAO scene: site area, footprint and its percentage, floor area, eaves and ridge heights, the setback of EVERY plot boundary with the building height facing...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-urbanisme.md
What cao_urbanisme does on Immobilier
AI agents call cao_urbanisme 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 |
|---|---|---|---|
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 |
regles | object | — | The rules read in the zone's regulation, e.g. {'recul_limites_m': 3, 'emprise_max_pct': 30, 'hauteur_max_m': 7}. |
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 |
Parameters from the server's own tool schema.
Why cao_urbanisme is rated Low
Even though cao_urbanisme 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 (95 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_urbanisme 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_urbanisme, this is the rule to start with:
cao_urbanisme 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_urbanisme call is checked against it from then on.
Questions about cao_urbanisme
WHEN a design must be checked against the LOCAL PLANNING RULES of its zone (French PLU) before a building-permit application. Measures on the CAO scene: site area, footprint and its percentage, floor area, eaves and ridge heights, the setback of EVERY plot boundary with the building height facing it, roof pitches, parking spaces, open ground; then checks them against the rules YOU pass in regles (recul_voie_m, recul_limites_m, prospect_h_sur_2, emprise_max_pct, hauteur_max_m, hauteur_max_faitage_m, pente_toit_min_deg, pente_toit_max_deg, stationnement_min, espaces_verts_min_pct). Each check returns the value, the threshold, whether it passes and what to change. NO planning value is ever invented: read the zone's regulation (Géoportail de l'urbanisme) and pass it. Without rules, the measurements alone are returned. It is categorised as a Read tool in the Immobilier MCP Server, which means it retrieves data without modifying state.
cao_urbanisme accepts 12 parameters: murs, plan, boites, georef, regles, cercles, reseaux, toitures, plomberie, decoration, ouvertures, electricite. 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_urbanisme: 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_urbanisme 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_urbanisme 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_urbanisme. 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_urbanisme 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