search_bodacc_announcements
Search French BODACC legal announcements by CRITERIA instead of by company — the monitoring question no other Sirenic tool answers: WHICH companies entered insolvency proceedings in department 59 this week? Pick a family (collective/insolvency proceedings, deregistrations, sales and transfers, in...
This record as markdown: /tools/eu-sirenic-sirenic/search-bodacc-announcements.md
What search_bodacc_announcements does on Sirenic
AI agents call search_bodacc_announcements to retrieve information from Sirenic 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 |
|---|---|---|---|
depuis | string | Yes | Start of the publication window, YYYY-MM-DD, e.g. 2026-08-04 |
api_key | string | — | Optional Sirenic API key (srn_live_…) to pay with prepaid credits instead of x402, with no wallet needed. Get one at https://api.sirenic.eu/compte?utm_source=ap |
famille | string | Yes | Family code (upstream BODACC codes): dpc (accounts filings, the largest family), modification, creation, radiation, collective (insolvency proceedings), vente, |
jusqu_a | string | — | Optional end of the window, YYYY-MM-DD |
x_payment | string | — | Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote. |
departement | string | — | Optional French department code: 01-95 except 20, 2A, 2B, 971-978 (e.g. 59 for Nord) |
Parameters from the server's own tool schema.
Why search_bodacc_announcements is rated Low
Even though search_bodacc_announcements 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.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs search_bodacc_announcements safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sirenic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_bodacc_announcements, this is the rule to start with:
search_bodacc_announcements 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 Sirenic, apply this rule, and every search_bodacc_announcements call is checked against it from then on.
Questions about search_bodacc_announcements
Search French BODACC legal announcements by CRITERIA instead of by company — the monitoring question no other Sirenic tool answers: WHICH companies entered insolvency proceedings in department 59 this week? Pick a family (collective/insolvency proceedings, deregistrations, sales and transfers, incorporations, accounts filings, conciliation, professional recovery, modifications, registrations, miscellaneous), a date window (depuis, optional jusqu_a) and optionally a French department code. Returns up to 100 announcements, newest first, each with SIREN, court, town, department and a STRUCTURED judgment (nature, date, family), plus tronque when there were more. The judgment's operative FREE TEXT is deliberately removed everywhere — it names court-appointed administrators with their address — so facts living only in that text (the date of cessation of payments, for one) are NOT here: follow url_bodacc, or get_french_company_alerts for a single company. Announcements about SOLE TRADERS are deliberately EXCLUDED (their name is personal data) and their count is returned in exclues_personnes_physiques, and records whose person type was unreadable are counted apart in exclues_type_indetermine (fail-closed guard). An announcement is not a verdict: the insolvency family also contains closures and cancellations — read the CURRENT state with get_french_company_alerts or get_french_company_failure_score. Paid via x402 ($0.03 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Read tool in the Sirenic MCP Server, which means it retrieves data without modifying state.
search_bodacc_announcements accepts 6 parameters: depuis, api_key, famille, jusqu_a, x_payment, departement. Required: depuis, famille. The full parameter table on this page comes from the server's own tool schema.
Register the Sirenic MCP server in PolicyLayer and add a rule for search_bodacc_announcements: 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 Sirenic. Nothing to install.
search_bodacc_announcements 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 search_bodacc_announcements 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 search_bodacc_announcements. 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.
search_bodacc_announcements is provided by the Sirenic MCP server (https://api.sirenic.eu/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sirenic, and thousands of servers like it.
This server
Across the catalogue