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

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

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

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.

ParameterTypeRequiredDescription
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

Questions about get_french_company_updates_since

What does the get_french_company_updates_since tool do? +

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.

What parameters does get_french_company_updates_since accept? +

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.

How do I enforce a policy on get_french_company_updates_since? +

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.

What risk level is get_french_company_updates_since? +

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

Can I rate-limit get_french_company_updates_since? +

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.

How do I block get_french_company_updates_since completely? +

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.

What MCP server provides get_french_company_updates_since? +

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.

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