# search_by_nace

Find Czech companies by CZ-NACE activity code (economic sector classification). Example: "62" = IT, "47" = retail, "86" = healthcare. Optional city filter. Useful for market research.

Agent View of the PolicyLayer registry record for `search_by_nace`. HTML page: https://policylayer.com/tools/dev-cz-agents-ares/search-by-nace

## Facts

- Tool: `search_by_nace`
- Server: Ares (`https://ares.cz-agents.dev/mcp`) — https://policylayer.com/tools/dev-cz-agents-ares.md
- Homepage: https://github.com/martinhavel/cz-agents-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 3 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `city` | string | no | Optional city filter. |
| `nace` | string | yes | CZ-NACE code, 2-6 digits (e.g., "62" for IT, "62010" for programming services). |
| `pocet` | integer | no | Max results. |

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": "search_by_nace",
    "arguments": {
      "nace": "<nace>"
    }
  }
}
```

## Why search_by_nace is rated Low

This tool retrieves and queries publicly available business register data without creating, modifying, or deleting records. It produces search results based on input parameters (NACE code and optional city), making it a classic Read operation with minimal blast radius even if misused by an agent.

From the tool's own definition: "Tool performs lookup and search operations ('Find Czech companies by CZ-NACE activity code') with optional filtering ('Optional city filter')."

## Use case

AI agents call search_by_nace to retrieve information from Ares 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 Ares:

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

## Other tools on Ares (9)

- `check_vat_payer` — Read — https://policylayer.com/tools/dev-cz-agents-ares/check-vat-payer.md
- `get_bank_accounts` — Read — https://policylayer.com/tools/dev-cz-agents-ares/get-bank-accounts.md
- `get_history` — Read — https://policylayer.com/tools/dev-cz-agents-ares/get-history.md
- `get_statutaries` — Read — https://policylayer.com/tools/dev-cz-agents-ares/get-statutaries.md
- `lookup_by_ico` — Read — https://policylayer.com/tools/dev-cz-agents-ares/lookup-by-ico.md
- `search_by_address` — Read — https://policylayer.com/tools/dev-cz-agents-ares/search-by-address.md
- `search_companies` — Read — https://policylayer.com/tools/dev-cz-agents-ares/search-companies.md
- `validate_dic` — Read — https://policylayer.com/tools/dev-cz-agents-ares/validate-dic.md
- `watch_entity` — Write — https://policylayer.com/tools/dev-cz-agents-ares/watch-entity.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=dev-cz-agents-ares · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-cz-agents-ares