prospect_french_companies
French B2B prospecting and lead generation: build company lists over the full French registry, filtered by NAF activity code, departement/postal code, legal form, workforce, age, RGE certification, gender-equality index. Returns up to 100 active companies per page; each page is one x402 payment (...
This record as markdown: /tools/eu-sirenic-sirenic/prospect-french-companies.md
What prospect_french_companies does on Sirenic
AI agents invoke prospect_french_companies to trigger actions in Sirenic. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
naf | string | — | NAF/APE code or prefix, at least two digits (62, 62.0, 62.01, 62.01Z): only the NAF rev. 2 form is retained (sub-class 62.01Z, and its levels: division 62, grou |
rge | boolean | — | true = active RGE environmental certification |
page | integer | — | Page number (one payment per page) |
age_max | integer | — | Maximum company age in years |
age_min | integer | — | Minimum company age in years |
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. |
egapro_min | integer | — | Minimum gender-equality index (0-100) |
code_postal | string | — | Postal-code prefix (2-5 digits), exclusive with departement |
departement | string | — | French departement: 75, 2A, 971… |
effectif_max | integer | — | Maximum workforce (number of employees) |
effectif_min | integer | — | Minimum workforce (number of employees) |
Parameters from the server's own tool schema.
Why prospect_french_companies is rated High
prospect_french_companies triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsHandles credentials or secrets (api_key) · High parameter count (13 properties)
Attacks that exploit this kind of access
The rule that runs prospect_french_companies safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sirenic, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For prospect_french_companies, this is the rule to start with:
prospect_french_companies stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sirenic, apply this rule, and every prospect_french_companies call is checked against it from then on.
Questions about prospect_french_companies
French B2B prospecting and lead generation: build company lists over the full French registry, filtered by NAF activity code, departement/postal code, legal form, workforce, age, RGE certification, gender-equality index. Returns up to 100 active companies per page; each page is one x402 payment ($0.02 in USDC or EURC). When you report a result, cite its citation verbatim. It is categorised as a Execute tool in the Sirenic MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
prospect_french_companies accepts 12 parameters: naf, rge, page, age_max, age_min, api_key, x_payment, egapro_min, code_postal, departement, effectif_max, effectif_min. The full parameter table on this page comes from the server's own tool schema.
Register the Sirenic MCP server in PolicyLayer and add a rule for prospect_french_companies: 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.
prospect_french_companies is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the prospect_french_companies 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 prospect_french_companies. 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.
prospect_french_companies 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.
Across the catalogue