New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

cao_visite_plan

WHEN the building should be SEEN in motion rather than read on a flat plan — you direct the shot. IMPORTANT: call cao_verifier FIRST and fix every severite=critique (intégrité clos/couvert + escalier/lucarne). This endpoint REFUSES with HTTP 400 construction_critique if the scene still has critic...

SERVERImmobilier SOURCEhttps://synergieloc.fr/mcp
Medium RISK CLASS
Category Write
Parameters 120 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/fr-synergieloc-immobilier/cao-visite-plan.md

What cao_visite_plan does on Immobilier

AI agents use cao_visite_plan 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.

ParameterTypeRequiredDescription
fps integer — Images par seconde de la visite. 24 à 30 pour un rendu naturel ; au-delà, le fichier grossit sans gain visible.
mode string — 'deco' = furnished as modelled; 'nu' = bare shell (plaster).
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[].
chemin array — OPTIONAL: your own waypoints — replaces the computed path.
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
cadence object — Pacing. Interior is a WALK: above ~1600 mm/s the video is unwatchable.
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
duree_s number — Video length, 8–900 s (default 60). A real estate walkthrough runs 480–600 s; the path is ENRICHED with extra exterior revolutions to fill it with movement rath
reseaux array — Plumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type).
objectif object — Lens, full-frame equivalent mm. 20 = interior standard, 35 = exterior, 50 = closing shot. Below 16 mm the image goes fisheye.

Parameters from the server's own tool schema.

Why cao_visite_plan is rated Medium

An AI agent can call cao_visite_plan 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 signalsHigh parameter count (125 properties) · Bulk/mass operation — affects multiple targets

Questions about cao_visite_plan

What does the cao_visite_plan tool do? +

WHEN the building should be SEEN in motion rather than read on a flat plan — you direct the shot. IMPORTANT: call cao_verifier FIRST and fix every severite=critique (intégrité clos/couvert + escalier/lucarne). This endpoint REFUSES with HTTP 400 construction_critique if the scene still has critical construction defects — the 4K visit would show them. Apply fixes via REST /api/v1/cao/integrite {appliquer:true, revalider:true} then retry. DIRECT the 4K cinematic visit of a CAO scene: choose the LENS (focal length in mm, full-frame equivalent) and the CAMERA PATH. Returns a shooting plan {plan:{objectif, cadence, plans[], chemin[]}, alertes[], resume} where chemin is the full waypoint list (position/vise in mm, CAO axes x=right y=depth z=height). Rooms are detected automatically (walls → flood fill → room centres → path through doorways), one interior walk per storey plus the stair climb. Rendering is done by ONE engine, the browser GPU: paste plan into CAO editor → « Visite 4K » → « Plan de caméra piloté », or call window.CAD_startCinematicTour({plan}). To adjust: resend with a modified objectif/cadence, or send back an edited chemin (it is then used verbatim and checked). Lens catalogue (free, no key): GET /api/v1/cao/visite/objectifs. Requires API key. REST: /api/v1/cao/visite/plan. 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.

What parameters does cao_visite_plan accept? +

cao_visite_plan accepts 12 parameters: fps, mode, murs, plan, boites, chemin, georef, cadence, cercles, duree_s, reseaux, objectif. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cao_visite_plan? +

Register the Immobilier MCP server in PolicyLayer and add a rule for cao_visite_plan: 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.

What risk level is cao_visite_plan? +

cao_visite_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit cao_visite_plan? +

Yes. Add a rate_limit block to the cao_visite_plan 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.

How do I block cao_visite_plan completely? +

Set action: deny in the PolicyLayer policy for cao_visite_plan. 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.

What MCP server provides cao_visite_plan? +

cao_visite_plan 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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Immobilier's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.