cao_carnet
WHEN a house design must be ISSUED as a drawing set (a Revit-style sheet set), for a client, a planning application or a contractor. Builds numbered A3 or A1 sheets: cover with sheet list, site plan, one plan per storey, elevations, section, MEP plans per storey and schedules. Views are printed a...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-carnet.md
What cao_carnet does on Immobilier
AI agents invoke cao_carnet to trigger actions in Immobilier. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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 |
projet | object | — | Title block: titre, maitre_ouvrage (client), auteur, adresse, phase (ESQ, APS, APD, PC, PRO, DCE, EXE, DOE), format_feuille (A3 or A1), revisions [{indice, date |
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_carnet is rated High
cao_carnet triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (95 properties) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_carnet 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_carnet, this is the rule to start with:
cao_carnet stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_carnet call is checked against it from then on.
Questions about cao_carnet
WHEN a house design must be ISSUED as a drawing set (a Revit-style sheet set), for a client, a planning application or a contractor. Builds numbered A3 or A1 sheets: cover with sheet list, site plan, one plan per storey, elevations, section, MEP plans per storey and schedules. Views are printed at TRUE SCALE (1:50, 1:100, 1:200... the largest standard scale that fits, never a false one). Every sheet carries a title block (project, client, phase, sheet code and title, scale, revision, n/N), the revision table and an 8-character fingerprint of the model it came from. Returns JSON {feuilles:[{code, titre, echelle}], empreinte, html}: the html prints one page per sheet. It is categorised as a Execute tool in the Immobilier MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cao_carnet accepts 12 parameters: murs, plan, boites, georef, projet, 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_carnet: 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_carnet is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cao_carnet 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_carnet. 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_carnet 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