Decisions on asylum claims, by year, country of origin (coo) and country of asylum (coa). Each row breaks out dec_recognized, dec_other, dec_rejected, dec_closed and dec_total; response.total aggregates the same fields. coo/coa take UNHCR 3-letter codes (see list_countries).
Part of the Unhcr server.
Free to start. No card required.
AI agents call asylum_decisions to retrieve information from Unhcr without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though asylum_decisions only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"asylum_decisions": {}
}
}See the full Unhcr policy for all 24 tools.
These attack patterns abuse exactly the kind of access asylum_decisions gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Decisions on asylum claims, by year, country of origin (coo) and country of asylum (coa). Each row breaks out dec_recognized, dec_other, dec_rejected, dec_closed and dec_total; response.total aggregates the same fields. coo/coa take UNHCR 3-letter codes (see list_countries).. It is categorised as a Read tool in the Unhcr MCP Server, which means it retrieves data without modifying state.
Register the Unhcr MCP server in PolicyLayer and add a rule for 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 Unhcr. Nothing to install.
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 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 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.
asylum_decisions is provided by the Unhcr MCP server (https://gateway.pipeworx.io/unhcr/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 24 Unhcr tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.