cao_programme
WHEN you are asked to DESIGN a house from a brief ('3 bedrooms, open kitchen, 90 m²') rather than to check or edit an existing scene. Returns a complete single-storey house scene — walls, doors, windows, named rooms, roof — laid out to French dimensions (1.00 m corridor, 90 cm doors, bedrooms of ...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-programme.md
What cao_programme does on Immobilier
AI agents use cao_programme 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 |
|---|---|---|---|
bureau | boolean | — | Add a study with its own window. |
cellier | boolean | — | Add a utility and storage room off the corridor. |
cuisine | string | — | Kitchen open onto the living room (ouverte) or a separate room (fermee). |
toiture | string | — | Roof: gable (deux_pans), hip (quatre_pans) or flat (plat). |
chambres | integer | — | Number of bedrooms, 1 to 5: the first gets 11 m² or more, the others 9 m² or more. |
typologie | string | — | Force one layout type. Default: both are drawn; the one closest to surface_m2 (or the most compact) is returned, the other as a variant. |
surface_m2 | number | — | Target living area in m², met through the living room size and the bedroom depth; the remaining gap comes back as ecart_m2. |
salles_de_bain | integer | — | 1 or 2 bathrooms. Default: 1 up to 3 bedrooms, 2 beyond (the second one is a shower room). |
Parameters from the server's own tool schema.
Why cao_programme is rated Medium
An AI agent can call cao_programme 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs cao_programme 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_programme, this is the rule to start with:
cao_programme 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_programme call is checked against it from then on.
Questions about cao_programme
WHEN you are asked to DESIGN a house from a brief ('3 bedrooms, open kitchen, 90 m²') rather than to check or edit an existing scene. Returns a complete single-storey house scene — walls, doors, windows, named rooms, roof — laid out to French dimensions (1.00 m corridor, 90 cm doors, bedrooms of 9 m² and more, 1/6 glazing in living rooms, load-bearing walls keeping every slab span under 5.60 m) that passes cao_verifier with zero alerts, with its rooms and areas, and the other layout type as a variant. Two layouts: 'aile' (through living room and a night wing on a central corridor) and 'bandes' (day strip, corridor, night strip). Single-storey only for now. Then: cao_copilote to retouch, cao_verifier after any edit, cao_generer_ifc or cao_permis. 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_programme accepts 8 parameters: bureau, cellier, cuisine, toiture, chambres, typologie, surface_m2, salles_de_bain. 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_programme: 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_programme 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_programme 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_programme. 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_programme 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