cao_permis
WHEN a detached house is headed for a French BUILDING PERMIT (permis de construire, Cerfa 13406). Drafts the permit file from the CAO scene: the Cerfa figures (surface de plancher per R111-22 — inner face of façades, stair openings and parts under 1.80 m excluded; emprise au sol per R420-1; eaves...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-permis.md
What cao_permis does on Immobilier
AI agents use cao_permis 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. |
coupe | array | — | Optional section line AA as [x1, y1, x2, y2] in mm (CAO axes). Default: across the building through its stair. |
titre | string | — | Project title shown on the dossier's cover page. |
auteur | string | — | Optional: applicant or designer shown on the cover page. |
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_permis is rated Medium
An AI agent can call cao_permis 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 (97 properties)
Attacks that exploit this kind of access
The rule that runs cao_permis 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_permis, this is the rule to start with:
cao_permis 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_permis call is checked against it from then on.
Questions about cao_permis
WHEN a detached house is headed for a French BUILDING PERMIT (permis de construire, Cerfa 13406). Drafts the permit file from the CAO scene: the Cerfa figures (surface de plancher per R111-22 — inner face of façades, stair openings and parts under 1.80 m excluded; emprise au sol per R420-1; eaves and ridge heights; storeys), plus PCMI2 site plan, PCMI3 section, PCMI4 written notice and PCMI5 elevations. PCMI1, PCMI6, PCMI7 and PCMI8 (location map, landscape insertion, photos) are listed as 'à fournir' — never invented; a Géoportail link is given when the scene has georef. For an EXTENSION, mark the existing walls existant: true: existing and created areas are then separated, and the file says when a déclaration préalable is enough (up to 20 m² created, 40 m² in a PLU urban zone). Local zoning rules (PLU) are NOT checked. Call cao_verifier first. Returns JSON {cerfa, pieces[], notice[], alertes[], avertissement}; drawings are SVG strings. 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_permis accepts 12 parameters: murs, plan, coupe, titre, auteur, 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_permis: 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_permis 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_permis 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_permis. 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_permis 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