cao_familles
WHEN you place doors or windows in a scene and want real, orderable joinery instead of free-size holes: lists the parametric families (hinged door in the French 63/73/83/93 series, double, sliding, pocket and entrance doors, French window, sliding patio door; one- or two-leaf, tilt-and-turn and f...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-familles.md
What cao_familles does on Immobilier
AI agents call cao_familles 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.
Why cao_familles is rated Low
Even though cao_familles 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.
Attacks that exploit this kind of access
The rule that runs cao_familles 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_familles, this is the rule to start with:
cao_familles is read-only, so it stays allowed. 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_familles call is checked against it from then on.
Questions about cao_familles
WHEN you place doors or windows in a scene and want real, orderable joinery instead of free-size holes: lists the parametric families (hinged door in the French 63/73/83/93 series, double, sliding, pocket and entrance doors, French window, sliding patio door; one- or two-leaf, tilt-and-turn and fixed windows) with bounded parameters and the bay size each gives. An ouvertures[] entry declaring famille + parametres is checked (out-of-series values refused, accessibility per the French 24 December 2015 decree) and exported to IFC as a door/window type with shared geometry, lining and panels. Free, no key. It is categorised as a Read tool in the Immobilier MCP Server, which means it retrieves data without modifying state.
Register the Immobilier MCP server in PolicyLayer and add a rule for cao_familles: 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_familles is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cao_familles 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_familles. 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_familles 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.
This server
Across the catalogue