cao_generer_ifc

SERVERImmobilier SOURCEhttps://synergieloc.fr/mcp

High RISK CLASS

Category Execute

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-generer-ifc.md

WHAT IT DOES

What cao_generer_ifc does on Immobilier

AI agents invoke cao_generer_ifc 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[].
`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
`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).
`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
`armatures`	boolean	—	Add the reinforcement computed per Eurocode 2 (bars and slab meshes).
`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
`ouvertures`	array	—	Doors/windows embedded in a wall — used only by cao_pdf (elevations + axonometric view), no effect on dxf/metres.
`electricite`	array	—	Electrical symbols (outlets, switches, lights…) — used only by cao_pdf (dedicated technical plan + quantities), no effect on dxf/metres/render. Position: attach

Parameters from the server's own tool schema.

RISK

Why cao_generer_ifc is rated High

cao_generer_ifc 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 (95 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cao_generer_ifc 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_generer_ifc, this is the rule to start with:

cao_generer_ifc Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cao_generer_ifc": {
      "limits": [
        {
          "counter": "cao_generer_ifc_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Immobilier, apply this rule, and every cao_generer_ifc call is checked against it from then on.

FAQ

Questions about cao_generer_ifc

What does the cao_generer_ifc tool do? +

WHEN the drawing must leave as a real BIM file, openable in Revit/ArchiCAD/Solibri — not just a drawing. Draw a building scene and get an IFC4 file in millimetres: real spatial hierarchy (project/site/building/storeys), STABLE IFC GlobalIds (the same model keeps them across exports; pass projet_id; imported elements keep theirs), structural columns and beams (poteaux[], poutres[] become IfcColumn, IfcBeam; see GET /cao/schema), one named IfcSpace per room with its areas (floor, French habitable and Carrez), floor slabs cut by their stair openings, an IfcRoof, IfcStair flights, standard Pset/Qto quantities, and material layers carrying density and thermal conductivity. Wall/slab/door/window types, 2nd-level space boundaries, and Lambert-93 georeferencing (EPSG:2154, Scale 0.001) are included so Revit/Archicad can open a typed, located model. Declare compositions{} to replace type compositions. Doors/windows really cut their host wall (IfcOpeningElement + IfcRelFillsElement). Passes IFC4 schema and EXPRESS-rule validation. Validate locally with cao_valider_ifc (no buildingSMART account). Call cao_verifier first. Same scene as cao_generer_dxf. Returns a JSON object {ifc, elements, unites, schema}: the IFC file arrives INLINE as text in ifc — no download URL, nothing stored server-side, so write it to a .ifc file yourself. elements counts the IFC objects emitted and schema names the IFC version produced. Set armatures: true to add the reinforcement: IfcReinforcingBar with exact geometry for footings and lintels (aggregated to their host), one IfcReinforcingMesh per slab. 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.

What parameters does cao_generer_ifc accept? +

cao_generer_ifc accepts 12 parameters: murs, plan, boites, georef, cercles, reseaux, toitures, armatures, plomberie, decoration, ouvertures, electricite. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on cao_generer_ifc? +

Register the Immobilier MCP server in PolicyLayer and add a rule for cao_generer_ifc: 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_generer_ifc? +

cao_generer_ifc is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cao_generer_ifc? +

Yes. Add a rate_limit block to the cao_generer_ifc 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_generer_ifc completely? +

Set action: deny in the PolicyLayer policy for cao_generer_ifc. 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_generer_ifc? +

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

KEEP EXPLORING

More on Immobilier, and thousands of servers like it.

This server

All 70 Immobilier tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →