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

Agent View of the PolicyLayer registry record for `cao_visite_camera`. HTML page: https://policylayer.com/tools/fr-synergieloc-immobilier/cao-visite-camera

## Facts

- Tool: `cao_visite_camera`
- Server: Immobilier (`https://synergieloc.fr/mcp`) — https://policylayer.com/tools/fr-synergieloc-immobilier.md
- Homepage: https://github.com/https://synergieloc.fr/mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 12 (1 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `murs` | array | no | 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 | no | 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 | no | Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[]. |
| `depuis` | object | no | Starting viewpoint — same shape as a `chemin` waypoint. Omit for an overall view of the building. |
| `georef` | object | no | 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 | no | 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 | no | Plumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type). |
| `reglages` | object | no | 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 | no | 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 | no | Sanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite. |
| `decoration` | array | no | 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.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "cao_visite_camera",
    "arguments": {
      "actions": []
    }
  }
}
```

## 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 signals: High parameter count (113 properties)

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Immobilier:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cao_visite_camera": {
      "limits": [
        {
          "counter": "cao_visite_camera_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Immobilier (69)

- `cao_energie` — Destructive — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-energie.md
- `cao_nomenclatures` — Destructive — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-nomenclatures.md
- `cao_verifier` — Destructive — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-verifier.md
- `cao_bibliotheque_familles` — Execute — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-bibliotheque-familles.md
- `cao_carnet` — Execute — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-carnet.md
- `cao_generer_ifc` — Execute — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-generer-ifc.md
- `cao_livrer` — Execute — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-livrer.md
- `bonnes_pratiques` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/bonnes-pratiques.md
- `cao_4d` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-4d.md
- `cao_devis` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-devis.md
- `cao_familles` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-familles.md
- `cao_ids_verifier` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-ids-verifier.md
- `cao_pdf` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-pdf.md
- `cao_rendu` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-rendu.md
- `cao_urbanisme` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-urbanisme.md
- `pack_partenaire` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/pack-partenaire.md
- `annonce_location` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/annonce-location.md
- `avenant_revision_irl` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/avenant-revision-irl.md
- `avis_echeance` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/avis-echeance.md
- `bon_intervention` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/bon-intervention.md
- `candidature_locataire` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/candidature-locataire.md
- `cao_bcf_ifc` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-bcf-ifc.md
- `cao_comparer_versions` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-comparer-versions.md
- `cao_conflits_ifc` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-conflits-ifc.md
- `cao_copilote` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-copilote.md
- `cao_demo` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-demo.md
- `cao_documents` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-documents.md
- `cao_famille_essayer` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-famille-essayer.md
- `cao_familles_recharger` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-familles-recharger.md
- `cao_ferraillage` — Write — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-ferraillage.md
- …and 39 more: https://policylayer.com/tools/fr-synergieloc-immobilier.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=fr-synergieloc-immobilier · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/fr-synergieloc-immobilier