cao_bibliotheque_familles
WHEN a parametric family (custom shelf, window, bench…) must be reused across projects or shared: the account's family library, like Revit's family library. action=lister: your families then the public ones of others (anonymous author code); action=lire: one family, ready to copy into scene.famil...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-bibliotheque-familles.md
What cao_bibliotheque_familles does on Immobilier
AI agents invoke cao_bibliotheque_familles 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 |
|---|---|---|---|
nom | string | — | Family name in the library (lire, enregistrer), e.g. etagere_murale. |
action | string | Yes | lister | lire | enregistrer. |
auteur | string | — | Author code of someone else's public family (lire). |
famille | object | — | The family definition to save (enregistrer). |
version | integer | — | A given version (lire); default: the latest. |
publique | boolean | — | Share the family with everyone (enregistrer). |
Parameters from the server's own tool schema.
Why cao_bibliotheque_familles is rated High
cao_bibliotheque_familles 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.
Attacks that exploit this kind of access
The rule that runs cao_bibliotheque_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_bibliotheque_familles, this is the rule to start with:
cao_bibliotheque_familles 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Immobilier, apply this rule, and every cao_bibliotheque_familles call is checked against it from then on.
Questions about cao_bibliotheque_familles
WHEN a parametric family (custom shelf, window, bench…) must be reused across projects or shared: the account's family library, like Revit's family library. action=lister: your families then the public ones of others (anonymous author code); action=lire: one family, ready to copy into scene.familles (with its origin); action=enregistrer: save a new version of famille under nom (unchanged definition: no new version), publique to share it. Build and test the family first with cao_famille_essayer. 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.
cao_bibliotheque_familles accepts 6 parameters: nom, action, auteur, famille, version, publique. Required: action. The full parameter table on this page comes from the server's own tool schema.
Register the Immobilier MCP server in PolicyLayer and add a rule for cao_bibliotheque_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_bibliotheque_familles is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cao_bibliotheque_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_bibliotheque_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_bibliotheque_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.
Across the catalogue