suggest_company_names
FREE. French company name autocomplete: type the beginning of a company name and get up to 5 matches with SIREN, city, postcode, NAF code and active/ceased status. Use it FIRST to turn a name into the SIREN that every other Sirenic tool takes as input — no account, no API key, no payment. Source:...
This record as markdown: /tools/eu-sirenic-sirenic/suggest-company-names.md
What suggest_company_names does on Sirenic
AI agents invoke suggest_company_names 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 |
|---|---|---|---|
q | string | Yes | Start of the company name (3 characters minimum once cleaned up), or a 9-digit SIREN — labelled ("SIREN : 552 032 534") is fine. |
Parameters from the server's own tool schema.
Why suggest_company_names is rated High
suggest_company_names 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 signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs suggest_company_names 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 suggest_company_names, this is the rule to start with:
suggest_company_names 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 suggest_company_names call is checked against it from then on.
Questions about suggest_company_names
FREE. French company name autocomplete: type the beginning of a company name and get up to 5 matches with SIREN, city, postcode, NAF code and active/ceased status. Use it FIRST to turn a name into the SIREN that every other Sirenic tool takes as input — no account, no API key, no payment. Source: the official INSEE Sirene register (open data), companies and sole traders whose record is publicly diffusible. Matches the START of the name, then whole words; no typo tolerance and no match-confidence score — for those, plus the full profile, use search_french_companies ($0.002) and get_french_company_profile ($0.005). 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.
suggest_company_names accepts 1 parameter: q. Required: q. 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 suggest_company_names: 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.
suggest_company_names 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 suggest_company_names 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 suggest_company_names. 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.
suggest_company_names 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