cao_visite_camera
WHEN the automatic visit is good but ONE view is wrong — the façade is cut off, the ridge is out of frame, you want to step into the next room — and rewriting a whole chemin by hand would be absurd. PILOT the camera with a SEQUENCE OF ACTIONS instead of coordinates: ['avancer x3', 'pivoter_gauche...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-visite-camera.md
What cao_visite_camera does on Immobilier
AI agents invoke cao_visite_camera to trigger actions in Immobilier. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| 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. |
boites | array | — | Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[]. |
depuis | object | — | Starting viewpoint — same shape as a `chemin` waypoint. Omit for an overall view of the building. |
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 |
actions | array | Yes | Ordered sequence. Each item is an action code ('avancer'), a keyboard shortcut ('ctrl+8'), a repeat form ('avancer x3'), or {code, repetitions}. 200 items max. |
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). |
reglages | object | — | Step sizes. Defaults: 500 mm per move, 250 mm per altitude step, 15° per rotation, ×1.25 per zoom. `grand_pas: true` = the Shift key (×4). |
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 |
Parameters from the server's own tool schema.
Why cao_visite_camera is rated High
cao_visite_camera triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHigh parameter count (113 properties)
Attacks that exploit this kind of access
The rule that runs cao_visite_camera 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_visite_camera, this is the rule to start with:
cao_visite_camera stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_visite_camera call is checked against it from then on.
Questions about cao_visite_camera
WHEN the automatic visit is good but ONE view is wrong — the façade is cut off, the ridge is out of frame, you want to step into the next room — and rewriting a whole chemin by hand would be absurd. PILOT the camera with a SEQUENCE OF ACTIONS instead of coordinates: ['avancer x3', 'pivoter_gauche', 'monter', 'zoom_arriere']. Actions are named (avancer, reculer, gauche, droite, the four diagonals, monter, descendre, pivoter_gauche/droite, incliner_haut/bas, zoom_avant, zoom_arriere, vue_initiale, vue_ensemble, piece_suivante, piece_precedente) or given as the KEYBOARD SHORTCUT a human would press in the render studio ('ctrl+8' = forward, numeric keypad laid out as a compass rose). Same grammar both ways, so a view prepared here is reproduced exactly by hand. Start from depuis (any waypoint of a chemin from cao_visite_plan) or omit it for an overall view. POST THE SCENE TOO: it enables wall collision (a step that would end inside a partition is refused and explained, not silently applied) and the room landmarks. Returns {camera, etapes[] (state after EACH action, with the reason for refused steps), chemin[]} — feed chemin straight back to cao_visite_studio to render that exact viewpoint in 4K. Catalogue of actions and keys (free, no key): GET /api/v1/cao/visite/commandes. Requires API key. REST: /api/v1/cao/visite/camera. It is categorised as a Execute tool in the Immobilier MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
cao_visite_camera accepts 12 parameters: murs, plan, boites, depuis, georef, actions, cercles, reseaux, reglages, toitures, plomberie, decoration. Required: actions. 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_visite_camera: 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_visite_camera is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cao_visite_camera 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_visite_camera. 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_visite_camera 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.
Across the catalogue