cao_famille_essayer
WHEN a custom parametric object is needed that no catalogue has (a made-to-measure shelf, a counter, a pergola, a technical box): try a family DEFINED AS DATA, like a Revit family — typed and bounded parameters, derived formulas, constraints, and solids whose dimensions are expressions (arithmeti...
This record as markdown: /tools/fr-synergieloc-immobilier/cao-famille-essayer.md
What cao_famille_essayer does on Immobilier
AI agents use cao_famille_essayer to create or update resources in Immobilier, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Immobilier environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
famille | object | Yes | The family definition: libelle, categorie (mobilier, equipement, structure, menuiserie, divers), parametres {name: {defaut, min, max, entier, choix}}, formules |
parametres | object | — | Parameter values; defaults otherwise. |
Parameters from the server's own tool schema.
Why cao_famille_essayer is rated Medium
An AI agent can call cao_famille_essayer faster than any human can review: one bad instruction and it creates or modifies resources in Immobilier by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs cao_famille_essayer 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_famille_essayer, this is the rule to start with:
cao_famille_essayer stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_famille_essayer call is checked against it from then on.
Questions about cao_famille_essayer
WHEN a custom parametric object is needed that no catalogue has (a made-to-measure shelf, a counter, a pergola, a technical box): try a family DEFINED AS DATA, like a Revit family — typed and bounded parameters, derived formulas, constraints, and solids whose dimensions are expressions (arithmetic, comparisons, min/max/round, a if c else b; nothing else is evaluated). Returns the computed values, constraint findings and solids in mm. To place it, add the definition under familles and instances under instances in any CAO scene: they become boxes in plans, 3D and quantities, and typed IFC objects with their parameters. It is categorised as a Write tool in the Immobilier MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
cao_famille_essayer accepts 2 parameters: famille, parametres. Required: famille. 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_famille_essayer: 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_famille_essayer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the cao_famille_essayer 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_famille_essayer. 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_famille_essayer 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