cao_comparer_versions
WHEN two versions of a house design must be compared: what the client, the architect or another agent changed, and what it changes to the quantities (the basis of a change order). Elements are matched by geometry (wall end points, wall and position of an opening, type and position of an object), ...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-comparer-versions.md
What cao_comparer_versions does on Immobilier
AI agents use cao_comparer_versions 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 |
|---|---|---|---|
apres | object | Yes | The modified scene. |
avant | object | Yes | The original scene (same format as the other CAO tools). |
quantites | boolean | — | Also compare the quantity take-off, item by item. |
Parameters from the server's own tool schema.
Why cao_comparer_versions is rated Medium
An AI agent can call cao_comparer_versions 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_comparer_versions 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_comparer_versions, this is the rule to start with:
cao_comparer_versions 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_comparer_versions call is checked against it from then on.
Questions about cao_comparer_versions
WHEN two versions of a house design must be compared: what the client, the architect or another agent changed, and what it changes to the quantities (the basis of a change order). Elements are matched by geometry (wall end points, wall and position of an opening, type and position of an object), never by their index, so deleting one wall does not report every following wall as modified. Returns added, removed and modified elements field by field, and the quantity take-off difference item by item. 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_comparer_versions accepts 3 parameters: apres, avant, quantites. Required: apres, avant. 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_comparer_versions: 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_comparer_versions 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_comparer_versions 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_comparer_versions. 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_comparer_versions 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