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

get_french_company_intelligence

Use for a GO/NO-GO decision (credit, investment, partnership) on a French company. Company INTELLIGENCE report — every Sirenic block cross-referenced in one call: identity & officers, financials with 3-year trend, sector positioning vs NAF peers, failure-risk score, BODACC legal alerts, commercia...

SERVERSirenic SOURCEhttps://api.sirenic.eu/mcp
Low RISK CLASS
Category Read
Parameters 31 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-intelligence.md

What get_french_company_intelligence does on Sirenic

AI agents call get_french_company_intelligence 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
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_intelligence is rated Low

Even though get_french_company_intelligence 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 · Admin/system-level operation

Questions about get_french_company_intelligence

What does the get_french_company_intelligence tool do? +

Use for a GO/NO-GO decision (credit, investment, partnership) on a French company. Company INTELLIGENCE report — every Sirenic block cross-referenced in one call: identity & officers, financials with 3-year trend, sector positioning vs NAF peers, failure-risk score, BODACC legal alerts, commercial-court decisions linked to the company (Judilibre stock since 2024-12-31: counts, closed-list nature and role, official links; partial coverage stated — never « no litigation »), sanctions screening (6 official lists, company + each officer), public procurement (French DECP + EU TED), IP assets, cached capital structure, industrial-risk synthesis (Seveso/ICPE), AMF PSAN/SGP register statuses, HATVP lobbying summary and a live VIES VAT check. Returns closed-list SIGNALS traced to their register source, synthese.conclusions_interdites (closed list of what THIS report does not allow you to infer — never a probability of default, a credit rating or an absence of risk; plus group health, current situation, cash position or an established sanction when the read data cannot support them), a deterministic verdict (solide/correct/fragile/critique) with synthese.motifs_verdict (closed-list codes that decided it) and synthese.verdict_plafonne_par (name-match doubts that capped it at « correct »: when non-empty, read « correct » as « correct subject to verification »), and strengths/vigilance points. The financial block carries decalage_analytique (latest filing known at the register vs latest year analysed) and the summary says it when a newer filing exists. Since v1.7 the synthese also carries reserves (closed-list reading caveats: holding scope, newer filing not analysed, old accounts, unpublished cash, weak name matches, unavailable blocks…), portee (what the verdict covers), confiance_financiere (the score band) and par_domaine (ten domains, each in its own closed list, all projected from blocks already served) — the verdict word itself is unchanged. Every block states the official register it comes from and its as_of date, so the report is auditable offline once the Ed25519 signature is verified. Since 2026-09-06 a company with no computable financial ratio (in practice no public accounts) and no other adverse signal gets indeterminable — insufficient public data, neither good nor bad — instead of correct. The flagship due-diligence call. A SIREN whose administrative status or legal category is missing in Sirene is refused: 404 identite_incomplete (body: siren, champs_absents, fiche), never charged. Paid via x402 ($1.00 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_intelligence accept? +

get_french_company_intelligence accepts 3 parameters: siren, api_key, x_payment. Required: siren. 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_intelligence? +

Register the Sirenic MCP server in PolicyLayer and add a rule for get_french_company_intelligence: 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_intelligence? +

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

Can I rate-limit get_french_company_intelligence? +

Yes. Add a rate_limit block to the get_french_company_intelligence 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_intelligence completely? +

Set action: deny in the PolicyLayer policy for get_french_company_intelligence. 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_intelligence? +

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