get_history
Get historical record of a company (previous names, registered address changes, trade license history). Useful for due diligence.
This record as markdown: /tools/dev-cz-agents-ares/get-history.md
What get_history does on Ares
AI agents call get_history 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_history is rated Low
This tool queries and returns historical metadata about a company from the Czech Business Register. It performs no mutations, deletions, or irreversible operations. The data returned is already public (ARES is a public registry). The blast radius of misuse is minimal—an agent could only retrieve historical business information, which is the intended use case for due diligence.
From the tool's definition Tool retrieves 'historical record' of company data including 'previous names, registered address changes, trade license history'—all read-only lookups with no modification or deletion capability.
Attacks that exploit this kind of access
The rule that runs get_history 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_history, this is the rule to start with:
get_history 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_history call is checked against it from then on.
Questions about get_history
Get historical record of a company (previous names, registered address changes, trade license history). Useful for due diligence. It is categorised as a Read tool in the Ares MCP Server, which means it retrieves data without modifying state.
get_history 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_history: 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_history 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_history 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_history. 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_history 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