get_bank_accounts
Get transparent bank accounts published for this company (only available for VAT-registered subjects). Useful to verify payment details on an invoice match the company.
This record as markdown: /tools/dev-cz-agents-ares/get-bank-accounts.md
What get_bank_accounts does on Ares
AI agents call get_bank_accounts 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 get_bank_accounts is rated Low
This tool retrieves and queries publicly published financial data from a transparent accounts registry. It performs a read-only lookup operation with no capability to modify, delete, or execute code. The data retrieved is already public and published by the Czech Business Register. The use case described—verifying payment details on invoices—is a verification/lookup task.
From the tool's definition Tool name and description indicate retrieval of publicly available bank account information: 'Get transparent bank accounts published for this company' and 'only available for VAT-registered subjects'.
Attacks that exploit this kind of access
The rule that runs get_bank_accounts 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 get_bank_accounts, this is the rule to start with:
get_bank_accounts 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 get_bank_accounts call is checked against it from then on.
Questions about get_bank_accounts
Get transparent bank accounts published for this company (only available for VAT-registered subjects). Useful to verify payment details on an invoice match the company. It is categorised as a Read tool in the Ares MCP Server, which means it retrieves data without modifying state.
get_bank_accounts 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 get_bank_accounts: 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.
get_bank_accounts 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 get_bank_accounts 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 get_bank_accounts. 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.
get_bank_accounts 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