check_vat_payer
Check whether a Czech company is a registered VAT payer (plátce DPH). If yes, returns DIČ, financial office, and any transparent bank accounts (payment details).
This record as markdown: /tools/dev-cz-agents-ares/check-vat-payer.md
What check_vat_payer does on Ares
AI agents call check_vat_payer 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 |
|---|---|---|---|
ico | string | Yes | Czech IČO (7-8 digits). |
Parameters from the server's own tool schema.
Why check_vat_payer is rated Low
This is fundamentally a read operation: it queries public Czech business register data and returns whether a company is VAT-registered along with related public details. While it exposes bank account information (which could facilitate fraud if misused by a malicious agent), the tool itself performs no destructive, financial, or execution actions.
From the tool's definition Tool 'check_vat_payer' retrieves VAT payer status and associated metadata (DIČ, financial office, bank accounts). No modification, deletion, or financial transaction occurs—purely informational lookup.
Attacks that exploit this kind of access
The rule that runs check_vat_payer 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 check_vat_payer, this is the rule to start with:
check_vat_payer 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 check_vat_payer call is checked against it from then on.
Questions about check_vat_payer
Check whether a Czech company is a registered VAT payer (plátce DPH). If yes, returns DIČ, financial office, and any transparent bank accounts (payment details). It is categorised as a Read tool in the Ares MCP Server, which means it retrieves data without modifying state.
check_vat_payer accepts 1 parameter: ico. Required: ico. 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 check_vat_payer: 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.
check_vat_payer 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 check_vat_payer 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 check_vat_payer. 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.
check_vat_payer 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