cao_fusionner_versions
WHEN two people or agents changed the same house design in parallel, starting from the same version, and both changes must be kept (like synchronising with a Revit central model). Three-way merge, element by element and field by field: a change made on one side goes through; the same field change...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-fusionner-versions.md
What cao_fusionner_versions does on Immobilier
AI agents use cao_fusionner_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 |
|---|---|---|---|
base | object | Yes | The version both sides started from. |
locale | object | Yes | Your changed copy, started from `base`. |
central | object | Yes | The shared version as it is now (changed by others). |
resolutions | object | — | Optional: for each conflict id returned by a first call, "central" or "local". |
empreinte_base | string | — | Optional: sha256 of the base as you loaded it (sorted JSON, compact separators) — a different base is refused (409). |
Parameters from the server's own tool schema.
Why cao_fusionner_versions is rated Medium
An AI agent can call cao_fusionner_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.
Attacks that exploit this kind of access
The rule that runs cao_fusionner_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_fusionner_versions, this is the rule to start with:
cao_fusionner_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_fusionner_versions call is checked against it from then on.
Questions about cao_fusionner_versions
WHEN two people or agents changed the same house design in parallel, starting from the same version, and both changes must be kept (like synchronising with a Revit central model). Three-way merge, element by element and field by field: a change made on one side goes through; the same field changed differently on both sides, or an element deleted on one side and modified on the other, is returned as a conflict, never silently overwritten. An opening stays on its own wall even if the other side deleted a wall before it. Pass resolutions {conflict id: central | local} to settle conflicts. Elements keep a persistent identity (ifc_guid, equal to their IFC GlobalId, or your own external_id). Pass empreinte_base (SHA-256 of the base you loaded) to refuse a merge on another base; the answer gives the SHA-256 of the three versions and of the result. 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_fusionner_versions accepts 5 parameters: base, locale, central, resolutions, empreinte_base. Required: base, locale, central. 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_fusionner_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_fusionner_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_fusionner_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_fusionner_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_fusionner_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