search_by_address
Find all companies registered at a given Czech address. Useful for due diligence (virtual offices, shell companies), real estate research, or competitor mapping in a building.
This record as markdown: /tools/dev-cz-agents-ares/search-by-address.md
What search_by_address does on Ares
AI agents call search_by_address 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 |
|---|---|---|---|
psc | integer | — | Postal code (PSČ), optional. |
city | string | Yes | City name, e.g. "Praha". |
pocet | integer | — | Max results (default 20). |
street | string | Yes | Street name (nazev ulice), e.g. "Radlická". |
Parameters from the server's own tool schema.
Why search_by_address is rated Low
This is a straightforward query tool that retrieves publicly available company registration information from the Czech Business Register (ARES) based on an address filter. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The tool is designed for passive information lookup only.
From the tool's definition Tool performs a search/lookup operation ('Find all companies') against public business registry data by address parameter. No modification, deletion, or execution of external operations is involved.
Attacks that exploit this kind of access
The rule that runs search_by_address 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_address, this is the rule to start with:
search_by_address 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_address call is checked against it from then on.
Questions about search_by_address
Find all companies registered at a given Czech address. Useful for due diligence (virtual offices, shell companies), real estate research, or competitor mapping in a building. It is categorised as a Read tool in the Ares MCP Server, which means it retrieves data without modifying state.
search_by_address accepts 4 parameters: psc, city, pocet, street. Required: city, street. 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_address: 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_address 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_address 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_address. 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_address 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