unhcr.asylum.decisions
Get UNHCR asylum decision outcomes — recognized refugees, other positive decisions, rejections, and closed/withdrawn cases by year and country. Includes recognition rate context: recognized + other_positive = total granted protection. Filter by year, country of origin ISO3 (coo), or country of as...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/unhcr.asylum.decisions.md
What unhcr.asylum.decisions does on Apibase
AI agents call unhcr.asylum.decisions to retrieve information from Apibase 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 |
|---|---|---|---|
coa | string | — | ISO 3-letter country code for country of asylum, e.g. DEU (Germany), TUR (Turkey), COL (Colombia). Omit to include all asylum countries. |
coo | string | — | ISO 3-letter country code for country of origin, e.g. SYR (Syria), AFG (Afghanistan), UKR (Ukraine). Omit to include all origin countries. |
year | integer | — | Reference year for the statistics (1951–present). Omit to return all years (paginated). |
limit | integer | — | Number of records to return per page (1–100, default 10). |
Parameters from the server's own tool schema.
Why unhcr.asylum.decisions is rated Low
Tool retrieves historical asylum statistics from open UNHCR data with no side effects or modifications.
From the tool's definition Get UNHCR asylum decision outcomes, recognized refugees, rejections, filter by year and country.
Attacks that exploit this kind of access
The rule that runs unhcr.asylum.decisions safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unhcr.asylum.decisions, this is the rule to start with:
unhcr.asylum.decisions 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 Apibase, apply this rule, and every unhcr.asylum.decisions call is checked against it from then on.
Questions about unhcr.asylum.decisions
Get UNHCR asylum decision outcomes — recognized refugees, other positive decisions, rejections, and closed/withdrawn cases by year and country. Includes recognition rate context: recognized + other_positive = total granted protection. Filter by year, country of origin ISO3 (coo), or country of asylum ISO3 (coa). Covers 1951–present with aggregate totals. Paginated; default 10 items. UNHCR Data License — open humanitarian data, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
unhcr.asylum.decisions accepts 4 parameters: coa, coo, year, limit. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for unhcr.asylum.decisions: 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 Apibase. Nothing to install.
unhcr.asylum.decisions 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 unhcr.asylum.decisions 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 unhcr.asylum.decisions. 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.
unhcr.asylum.decisions is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue