get_french_company_updates_since
What changed at a French company since a date ("what changed at this customer since June?"): every official block in one call, namely BODACC notices (insolvency, sales, deregistration, changes, accounts filings with their figures), commercial-court decisions, French and EU public contracts, estab...
This record as markdown: /tools/eu-sirenic-sirenic/get-french-company-updates-since.md
What get_french_company_updates_since does on Sirenic
AI agents call get_french_company_updates_since 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 |
|---|---|---|---|
siren | string | Yes | 9-digit SIREN |
depuis | string | Yes | List what was published since this day, a past day or today. Accepts YYYY-MM-DD (a real date), or a full ISO 8601 timestamp (offset Z, ±HH:MM, ±HHMM or none, re |
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 |
x_payment | string | — | Optional signed x402 PAYMENT-SIGNATURE header value. Omit to receive the payment quote. |
Parameters from the server's own tool schema.
Why get_french_company_updates_since is rated Low
Even though get_french_company_updates_since 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) · Bulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get_french_company_updates_since 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 get_french_company_updates_since, this is the rule to start with:
get_french_company_updates_since 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 get_french_company_updates_since call is checked against it from then on.
Questions about get_french_company_updates_since
What changed at a French company since a date ("what changed at this customer since June?"): every official block in one call, namely BODACC notices (insolvency, sales, deregistration, changes, accounts filings with their figures), commercial-court decisions, French and EU public contracts, establishments opened or closed, cessation, licences, dated sanctions listings, trademarks, patents and designs, RGE certifications and the lobbying register. Each change is dated at publication with the event date alongside; verdict nouveautes, rien_de_nouveau (every block read in full and fresh) or lecture_incomplete (a block down, stale or partly read, named); monthly stocks (Sirene, French contracts) make a recent date, after their snapshot, yield lecture_incomplete, never rien_de_nouveau; the 100 most recent, per-type totals before the cut. Hiring, officers and headcount band are outside the engine. Paid via x402 ($0.05 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.
get_french_company_updates_since accepts 4 parameters: siren, depuis, api_key, x_payment. Required: siren, depuis. 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 get_french_company_updates_since: 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.
get_french_company_updates_since 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 get_french_company_updates_since 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 get_french_company_updates_since. 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.
get_french_company_updates_since 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