insee.establishment.by_siret
Retrieve the official record of a French establishment (physical site/branch) from the INSEE Sirene registry using its 14-digit SIRET number (SIREN + NIC). Returns the establishment status (active/closed), NAF activity code, creation date, full postal address (street, postal code, city), head-off...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/insee.establishment.by-siret.md
What insee.establishment.by_siret does on Apibase
AI agents call insee.establishment.by_siret 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 |
|---|---|---|---|
siret | string | Yes | SIRET establishment identifier — exactly 14 digits (SIREN + NIC, e.g. 55208131766522). Spaces are stripped automatically. |
Parameters from the server's own tool schema.
Why insee.establishment.by_siret is rated Low
Queries public French business registry; no modification, deletion, or execution of code.
From the tool's definition Retrieve official record, Returns establishment status, creation date, postal address
Attacks that exploit this kind of access
The rule that runs insee.establishment.by_siret 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.establishment.by_siret, this is the rule to start with:
insee.establishment.by_siret 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.establishment.by_siret call is checked against it from then on.
Questions about insee.establishment.by_siret
Retrieve the official record of a French establishment (physical site/branch) from the INSEE Sirene registry using its 14-digit SIRET number (SIREN + NIC). Returns the establishment status (active/closed), NAF activity code, creation date, full postal address (street, postal code, city), head-office flag, and the parent company (legal unit) record. The Sirene database covers ~40M French establishments; address data is geocoded by INSEE. Use insee.company.by_siren to look up only the parent company, or insee.establishment.search to find establishments by postal code or city. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
insee.establishment.by_siret accepts 1 parameter: siret. Required: siret. 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.establishment.by_siret: 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.establishment.by_siret 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.establishment.by_siret 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.establishment.by_siret. 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.establishment.by_siret 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