bonnes_pratiques
WHEN you discover this server — call it FIRST, before anything else, and again if your cached instructions may be stale. FREE versioned playbook of best practices for MCP/API agents (no API key, 0 units). Domains: securite, documents (window-envelope quittance/IRL), cao (verifier workflow, relati...
This record as markdown: /tools/fr-synergieloc-immobilier/bonnes-pratiques.md
What bonnes_pratiques does on Immobilier
AI agents call bonnes_pratiques 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
domaine | string | — | Optional filter. Omit to receive all domains. |
Parameters from the server's own tool schema.
Why bonnes_pratiques is rated Low
Even though bonnes_pratiques 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 bonnes_pratiques 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 bonnes_pratiques, this is the rule to start with:
bonnes_pratiques 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 bonnes_pratiques call is checked against it from then on.
Questions about bonnes_pratiques
WHEN you discover this server — call it FIRST, before anything else, and again if your cached instructions may be stale. FREE versioned playbook of best practices for MCP/API agents (no API key, 0 units). Domains: securite, documents (window-envelope quittance/IRL), cao (verifier workflow, relative sill, dormers), irl, workflow. Returns {version, domaines{…regles[{id,titre,regle,corriger}]}, urls}. Contains NO tenant data — public rules only; server-side guardrails remain authoritative. REST: GET /api/v1/agent-playbook?domaine=cao. It is categorised as a Read tool in the Immobilier MCP Server, which means it retrieves data without modifying state.
bonnes_pratiques accepts 1 parameter: domaine. 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 bonnes_pratiques: 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.
bonnes_pratiques 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 bonnes_pratiques 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 bonnes_pratiques. 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.
bonnes_pratiques 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