insee.company.by_siren
Retrieve the official record of a French legal unit (company, association, sole trader) from the INSEE Sirene national registry using its 9-digit SIREN identifier. Returns the current company name, acronym, administrative status (active/ceased), NAF/APE activity code, legal category code, creatio...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/insee.company.by-siren.md
What insee.company.by_siren does on Apibase
AI agents call insee.company.by_siren to retrieve information from Apibase 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 | SIREN company identifier — exactly 9 digits (e.g. 552081317 for EDF). Spaces are stripped automatically. |
Parameters from the server's own tool schema.
Why insee.company.by_siren is rated Low
Retrieves company metadata from public registry; no modification, deletion, or execution capability.
From the tool's definition Retrieve the official record... Returns the current company name, acronym, administrative status, NAF/APE activity code, legal category code, creation date, company-size band, and head-office NIC.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs insee.company.by_siren safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For insee.company.by_siren, this is the rule to start with:
insee.company.by_siren 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 Apibase, apply this rule, and every insee.company.by_siren call is checked against it from then on.
Questions about insee.company.by_siren
Retrieve the official record of a French legal unit (company, association, sole trader) from the INSEE Sirene national registry using its 9-digit SIREN identifier. Returns the current company name, acronym, administrative status (active/ceased), NAF/APE activity code, legal category code, creation date, company-size band (TPE/PME/ETI/GE), and head-office NIC. The Sirene database covers all ~30M French legal units registered since 1973, updated daily. Use insee.establishment.by_siret for physical address and site-level details, or insee.company.search to find companies by name or activity code. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
insee.company.by_siren accepts 1 parameter: siren. Required: siren. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for insee.company.by_siren: 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 Apibase. Nothing to install.
insee.company.by_siren 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 insee.company.by_siren 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 insee.company.by_siren. 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.
insee.company.by_siren is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue