# get_company_profile

Fetch a single Romanian company by CUI (accepts an 'RO' prefix): identity, address, CAEN activities, latest public financials, and data-source freshness. Does not return contact details.

Agent View of the PolicyLayer registry record for `get_company_profile`. HTML page: https://policylayer.com/tools/com-firmeromanesti-company-data/get-company-profile

## Facts

- Tool: `get_company_profile`
- Server: Company Data (`https://firmeromanesti.com/mcp`) — https://policylayer.com/tools/com-firmeromanesti-company-data.md
- Homepage: https://github.com/QwertyBit-Ventures/firmeromanesti
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server auth posture: open
- Server CORS policy: *
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `cui` | object | yes |  |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_company_profile",
    "arguments": {
      "cui": {}
    }
  }
}
```

## Why get_company_profile is rated Low

This tool queries and retrieves company profile information (identity, address, CAEN activities, financials) by CUI identifier. It is a straightforward data retrieval operation with no capability to modify, delete, execute code, or trigger external operations. The read-only constraint and absence of contact details further confirm this is a safe informational lookup.

From the tool's own definition: "Tool description states 'Fetch a single Romanian company' and 'Does not return contact details.' The server is explicitly described as 'Read-only data.' The tool performs retrieval only with no modification or side effects."

## Use case

AI agents call get_company_profile 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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Company Data:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_company_profile": {}
  }
}
```

## Other tools on Company Data (4)

- `get_company_financials` — Read — https://policylayer.com/tools/com-firmeromanesti-company-data/get-company-financials.md
- `get_company_status` — Read — https://policylayer.com/tools/com-firmeromanesti-company-data/get-company-status.md
- `resolve_caen` — Read — https://policylayer.com/tools/com-firmeromanesti-company-data/resolve-caen.md
- `search_companies` — Read — https://policylayer.com/tools/com-firmeromanesti-company-data/search-companies.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=com-firmeromanesti-company-data · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-firmeromanesti-company-data