New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

unhcr.asylum.applications

Get UNHCR asylum application counts — number of new asylum claims filed by year and country. Data includes procedure type (G=Government, U=UNHCR), application type (N=New, A=Appeal), decision level (FI=First Instance, AR=Appeal/Review), and applicant category (P=Person). Filter by year, country o...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/unhcr.asylum.applications.md

What unhcr.asylum.applications does on Apibase

AI agents call unhcr.asylum.applications 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.

ParameterTypeRequiredDescription
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.applications is rated Low

Retrieves historical asylum statistics from public UNHCR datasets with no side effects or data modification.

From the tool's definition Get UNHCR asylum application counts, number of new asylum claims filed by year and country.

Questions about unhcr.asylum.applications

What does the unhcr.asylum.applications tool do? +

Get UNHCR asylum application counts — number of new asylum claims filed by year and country. Data includes procedure type (G=Government, U=UNHCR), application type (N=New, A=Appeal), decision level (FI=First Instance, AR=Appeal/Review), and applicant category (P=Person). Filter by year, country of origin ISO3 (coo), or country of asylum ISO3 (coa). Covers 1951–present with totals when available. 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.

What parameters does unhcr.asylum.applications accept? +

unhcr.asylum.applications accepts 4 parameters: coa, coo, year, limit. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on unhcr.asylum.applications? +

Register the Apibase MCP server in PolicyLayer and add a rule for unhcr.asylum.applications: 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.

What risk level is unhcr.asylum.applications? +

unhcr.asylum.applications is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit unhcr.asylum.applications? +

Yes. Add a rate_limit block to the unhcr.asylum.applications 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.

How do I block unhcr.asylum.applications completely? +

Set action: deny in the PolicyLayer policy for unhcr.asylum.applications. 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.

What MCP server provides unhcr.asylum.applications? +

unhcr.asylum.applications 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.