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.
This record as markdown: /tools/dev-cz-agents-ares/search-by-nace.md
What search_by_nace does on Ares
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.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | Optional city filter. |
nace | string | Yes | CZ-NACE code, 2-6 digits (e.g., "62" for IT, "62010" for programming services). |
pocet | integer | — | Max results. |
Parameters from the server's own tool schema.
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 definition Tool performs lookup and search operations ('Find Czech companies by CZ-NACE activity code') with optional filtering ('Optional city filter').
Attacks that exploit this kind of access
The rule that runs search_by_nace safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ares, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_by_nace, this is the rule to start with:
search_by_nace 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 Ares, apply this rule, and every search_by_nace call is checked against it from then on.
Questions about 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. It is categorised as a Read tool in the Ares MCP Server, which means it retrieves data without modifying state.
search_by_nace accepts 3 parameters: city, nace, pocet. Required: nace. The full parameter table on this page comes from the server's own tool schema.
Register the Ares MCP server in PolicyLayer and add a rule for search_by_nace: 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 Ares. Nothing to install.
search_by_nace 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 search_by_nace 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 search_by_nace. 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.
search_by_nace is provided by the Ares MCP server (https://ares.cz-agents.dev/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ares, and thousands of servers like it.
This server
Across the catalogue