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

insee.establishment.search

Search French establishments (physical sites, branches, stores) in the INSEE Sirene registry using a Lucene-style filter query. Supports filtering by postal code (codePostalEtablissement, e.g. "75008"), city name (libelleCommuneEtablissement, e.g. "PARIS"), NAF activity code (activitePrincipaleEt...

SERVERApibase SOURCEapibase-mcp-client
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/io-github-whiteknightonhorse-apibase/insee.establishment.search.md

What insee.establishment.search does on Apibase

AI agents call insee.establishment.search 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.

ParameterTypeRequiredDescription
q string Yes Lucene-style filter expression on establishment fields. Examples: "codePostalEtablissement:75008" searches by French postal code; "libelleCommuneEtablissement:P
max integer — Maximum number of results to return (1–20, default 10).
offset integer — Zero-based starting offset for pagination (default 0).

Parameters from the server's own tool schema.

Why insee.establishment.search is rated Low

Tool retrieves establishment data from public business registry with no side effects.

From the tool's definition Search French establishments in INSEE Sirene registry using Lucene-style filter query.

Questions about insee.establishment.search

What does the insee.establishment.search tool do? +

Search French establishments (physical sites, branches, stores) in the INSEE Sirene registry using a Lucene-style filter query. Supports filtering by postal code (codePostalEtablissement, e.g. "75008"), city name (libelleCommuneEtablissement, e.g. "PARIS"), NAF activity code (activitePrincipaleEtablissement, e.g. "47.11B" for supermarkets), status (etatAdministratifEtablissement: A=active, F=closed), and parent company name (denominationUniteLegale). Combine clauses with AND / OR operators. Returns SIRET, address, status, NAF code, head-office flag, and parent company summary for each matching establishment. Use insee.establishment.by_siret to retrieve full details for a specific SIRET. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does insee.establishment.search accept? +

insee.establishment.search accepts 3 parameters: q, max, offset. Required: q. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on insee.establishment.search? +

Register the Apibase MCP server in PolicyLayer and add a rule for insee.establishment.search: 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.

What risk level is insee.establishment.search? +

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

Can I rate-limit insee.establishment.search? +

Yes. Add a rate_limit block to the insee.establishment.search 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 insee.establishment.search completely? +

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

insee.establishment.search 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.

Across the catalogue

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