get_company_status
Public status flags for a company by CUI: registration status, VAT (TVA) registration, fiscal activity, insolvency, dissolution (radiere), and e-Factura.
This record as markdown: /tools/com-firmeromanesti-company-data/get-company-status.md
What get_company_status does on Company Data
AI agents call get_company_status to retrieve information from Company Data 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 |
|---|---|---|---|
cui | object | Yes |
Parameters from the server's own tool schema.
Why get_company_status is rated Low
This tool performs a straightforward lookup of publicly available company status information. It has no side effects, does not modify data, does not execute code, and does not trigger external actions. The data returned is informational only (registration, tax, and dissolution status). This is a standard Read operation with low risk of harm even in misuse scenarios, as it only exposes already-public information.
From the tool's definition Tool retrieves 'public status flags' (registration status, VAT registration, fiscal activity, insolvency, dissolution, e-Factura) for a company—a pure query operation with no modification, deletion, or code execution.
Attacks that exploit this kind of access
The rule that runs get_company_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Company Data, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_company_status, this is the rule to start with:
get_company_status 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 Company Data, apply this rule, and every get_company_status call is checked against it from then on.
Questions about get_company_status
Public status flags for a company by CUI: registration status, VAT (TVA) registration, fiscal activity, insolvency, dissolution (radiere), and e-Factura. It is categorised as a Read tool in the Company Data MCP Server, which means it retrieves data without modifying state.
get_company_status accepts 1 parameter: cui. Required: cui. The full parameter table on this page comes from the server's own tool schema.
Register the Company Data MCP server in PolicyLayer and add a rule for get_company_status: 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 Company Data. Nothing to install.
get_company_status 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 get_company_status 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 get_company_status. 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.
get_company_status is provided by the Company Data MCP server (https://firmeromanesti.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Company Data, and thousands of servers like it.
This server
Across the catalogue