# cao_4d

WHEN the building must be shown AS IT WILL BE BUILT over time (4D, as Navisworks links a model to a schedule): every element belongs to a trade (load-bearing walls to structural works, roof to roofing, facade openings to exterior joinery, partitions and rooms to drywall, interior doors and stairs to interior joinery, finishes, furniture at handover); the schedule comes from the model's quantities. Returns one step per trade with its dates and, as SVG, the axonometric view and the ground-floor plan as built at the end of that trade, and optionally the state at a given date.

Agent View of the PolicyLayer registry record for `cao_4d`. HTML page: https://policylayer.com/tools/fr-synergieloc-immobilier/cao-4d

## Facts

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

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `date` | string | no | Optional date, YYYY-MM-DD: the state of the site on that day. |
| `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. |
| `debut` | string | no | Site start date, YYYY-MM-DD (today by default). |
| `boites` | array | no | Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[]. |
| `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 |
| `images` | boolean | no | Include the SVG views. |
| `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). |
| `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_4d",
    "arguments": {}
  }
}
```

## Why cao_4d is rated Low

Even though cao_4d only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signals: High parameter count (97 properties)

## Use case

AI agents call cao_4d to retrieve information from Immobilier without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

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

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "cao_4d": {}
  }
}
```

## 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
- `cao_visite_camera` — Execute — https://policylayer.com/tools/fr-synergieloc-immobilier/cao-visite-camera.md
- `bonnes_pratiques` — Read — https://policylayer.com/tools/fr-synergieloc-immobilier/bonnes-pratiques.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