get_population_data
AI agents call get_population_data to retrieve information from UNHCR Population Data MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves UNHCR refugee statistics based on query parameters (country of origin, country of asylum, year). The 'get_' prefix and context of public statistical data access indicate a read-only operation with no side effects. While the tool description is empty, the server's stated purpose and sibling tool naming conventions strongly suggest data retrieval.
From the tool's definition Tool name 'get_population_data' with sibling tools named 'get_demographics_data', 'get_rsd_applications', 'get_rsd_decisions', and 'get_solutions' all follow a consistent query pattern.
Attacks that exploit this kind of access
get_population_data. It is categorised as a Read tool in the UNHCR Population Data MCP Server MCP Server, which means it retrieves data without modifying state.
Register the UNHCR Population Data MCP Server MCP server in PolicyLayer and add a rule for get_population_data: 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 Population Data MCP Server. Nothing to install.
get_population_data 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 get_population_data 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 get_population_data. 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.
get_population_data is provided by the UNHCR Population Data MCP Server MCP server (rvibek/mcp_unhcr). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →