cao_soleil
WHEN a design decision depends on the SUN: how many hours of direct sunlight each window actually receives, where the building casts its shadow on the plot, and whether a neighbouring building or screen blocks the light. From the CAO scene, for the three dates that decide a project (21 June, 21 M...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-soleil.md
What cao_soleil does on Immobilier
AI agents use cao_soleil 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. |
annee | integer | — | Optional year for the three reference dates. |
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). |
nord_deg | number | — | Direction of north in the scene, in degrees clockwise from +y (0 means +y is north). |
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. |
Parameters from the server's own tool schema.
Why cao_soleil is rated Medium
An AI agent can call cao_soleil 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_soleil 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_soleil, this is the rule to start with:
cao_soleil 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_soleil call is checked against it from then on.
Questions about cao_soleil
WHEN a design decision depends on the SUN: how many hours of direct sunlight each window actually receives, where the building casts its shadow on the plot, and whether a neighbouring building or screen blocks the light. From the CAO scene, for the three dates that decide a project (21 June, 21 March, 21 December): sunrise, sunset, maximum altitude, the shadow at solar noon (area and outline), and per window the hours of sun with the first and last hour, its orientation and its azimuth. Obstacles are the building's own walls and roof plus any masques you declare. The site comes from georef (Lambert-93); without it Strasbourg is used and the answer says so. No solar gain in watts and no RE 2020 discomfort hours: those need a dynamic thermal engine. 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_soleil accepts 12 parameters: murs, plan, annee, boites, georef, cercles, reseaux, nord_deg, toitures, plomberie, decoration, ouvertures. 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_soleil: 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_soleil 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_soleil 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_soleil. 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_soleil 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