# get_history

Get historical record of a company (previous names, registered address changes, trade license history). Useful for due diligence.

Agent View of the PolicyLayer registry record for `get_history`. HTML page: https://policylayer.com/tools/dev-cz-agents-ares/get-history

## Facts

- Tool: `get_history`
- Server: Ares (`https://ares.cz-agents.dev/mcp`) — https://policylayer.com/tools/dev-cz-agents-ares.md
- Homepage: https://github.com/martinhavel/cz-agents-mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: yes
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `ico` | string | yes | Czech IČO (7-8 digits). |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_history",
    "arguments": {
      "ico": "<ico>"
    }
  }
}
```

## 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 own 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."

## Use case

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.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Ares:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_history": {}
  }
}
```

## Other tools on Ares (9)

- `check_vat_payer` — Read — https://policylayer.com/tools/dev-cz-agents-ares/check-vat-payer.md
- `get_bank_accounts` — Read — https://policylayer.com/tools/dev-cz-agents-ares/get-bank-accounts.md
- `get_statutaries` — Read — https://policylayer.com/tools/dev-cz-agents-ares/get-statutaries.md
- `lookup_by_ico` — Read — https://policylayer.com/tools/dev-cz-agents-ares/lookup-by-ico.md
- `search_by_address` — Read — https://policylayer.com/tools/dev-cz-agents-ares/search-by-address.md
- `search_by_nace` — Read — https://policylayer.com/tools/dev-cz-agents-ares/search-by-nace.md
- `search_companies` — Read — https://policylayer.com/tools/dev-cz-agents-ares/search-companies.md
- `validate_dic` — Read — https://policylayer.com/tools/dev-cz-agents-ares/validate-dic.md
- `watch_entity` — Write — https://policylayer.com/tools/dev-cz-agents-ares/watch-entity.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=dev-cz-agents-ares · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/dev-cz-agents-ares