New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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...

SERVERSirenic SOURCEhttps://api.sirenic.eu/mcp
Low RISK CLASS
Category Read
Parameters 62 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about search_bodacc_announcements

What does the search_bodacc_announcements tool do? +

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.

What parameters does search_bodacc_announcements accept? +

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.

How do I enforce a policy on search_bodacc_announcements? +

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.

What risk level is search_bodacc_announcements? +

search_bodacc_announcements is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_bodacc_announcements? +

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.

How do I block search_bodacc_announcements completely? +

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.

What MCP server provides search_bodacc_announcements? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sirenic's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.