# validate_iin

Validate a Kazakhstan IIN/BIN (real national checksum) + parse structure (person: birth date/sex; entity: registration). Free.

Agent View of the PolicyLayer registry record for `validate_iin`. HTML page: https://policylayer.com/tools/com-get4agent-marketplace/validate-iin

## Facts

- Tool: `validate_iin`
- Server: Marketplace (`https://get4agent.com/mcp`) — https://policylayer.com/tools/com-get4agent-marketplace.md
- Homepage: https://github.com/https://get4agent.com/mcp
- Risk category: Read (Low risk)
- Registry record: grade C, identity unverified
- Server auth posture: open
- Server rate-limited: no
- Parameters: 1 (1 required)
- Recommended policy verdict: Allowed

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `iin` | string | yes |  |

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": "validate_iin",
    "arguments": {
      "iin": "<iin>"
    }
  }
}
```

## Why validate_iin is rated Low

Even though validate_iin only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

## Use case

AI agents call validate_iin to retrieve information from Marketplace 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 Marketplace:

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

## Other tools on Marketplace (9)

- `fx_rates` — Read — https://policylayer.com/tools/com-get4agent-marketplace/fx-rates.md
- `get_listing` — Read — https://policylayer.com/tools/com-get4agent-marketplace/get-listing.md
- `kzt_rates` — Read — https://policylayer.com/tools/com-get4agent-marketplace/kzt-rates.md
- `lei_lookup` — Read — https://policylayer.com/tools/com-get4agent-marketplace/lei-lookup.md
- `search_listings` — Read — https://policylayer.com/tools/com-get4agent-marketplace/search-listings.md
- `track_parcel` — Read — https://policylayer.com/tools/com-get4agent-marketplace/track-parcel.md
- `validate_kz_iban` — Read — https://policylayer.com/tools/com-get4agent-marketplace/validate-kz-iban.md
- `verify_agent` — Read — https://policylayer.com/tools/com-get4agent-marketplace/verify-agent.md
- `weather` — Read — https://policylayer.com/tools/com-get4agent-marketplace/weather.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=com-get4agent-marketplace · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/com-get4agent-marketplace