cao_copilote
WHEN a user asks to change an existing building scene in plain words — « agrandis la cuisine d'un mètre », « réduis la chambre 2 de 50 cm côté nord », move a wall, widen a door, move or rotate furniture: the request becomes typed operations (catalogue: GET /api/v1/cao/copilote), executed to the m...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-copilote.md
What cao_copilote does on Immobilier
AI agents use cao_copilote 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 |
|---|---|---|---|
scene | object | Yes | The building scene to modify (same format as cao_generer_ifc: murs, ouvertures, mobilier…). |
modele | boolean | — | False to use only the deterministic rules, never the language model. |
operations | array | — | Optional typed operations (GET /api/v1/cao/copilote) applied without the language model. |
instruction | string | — | The request in natural language, e.g. « agrandis la cuisine d'un mètre ». |
Parameters from the server's own tool schema.
Why cao_copilote is rated Medium
An AI agent can call cao_copilote 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.
Attacks that exploit this kind of access
The rule that runs cao_copilote 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_copilote, this is the rule to start with:
cao_copilote 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_copilote call is checked against it from then on.
Questions about cao_copilote
WHEN a user asks to change an existing building scene in plain words — « agrandis la cuisine d'un mètre », « réduis la chambre 2 de 50 cm côté nord », move a wall, widen a door, move or rotate furniture: the request becomes typed operations (catalogue: GET /api/v1/cao/copilote), executed to the millimetre (attached walls extended, furniture against the wall follows it, objects in the way pushed, switches moved out of door openings), then the result is re-checked by our controls. A wall that would create a defect is not used; a load-bearing wall stacked with another storey never moves alone. Returns {compris, source, operations, journal, erreurs, nouvelles_alertes, valide, scene, difference}; send scene on to cao_generer_ifc or cao_pdf. 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_copilote accepts 4 parameters: scene, modele, operations, instruction. Required: scene. 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_copilote: 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_copilote 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_copilote 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_copilote. 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_copilote 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