who.health.data
Retrieve WHO health data for a specific indicator, optionally filtered by country and year range. Returns values for up to 194 countries spanning multiple decades. Official UN member state reporting data.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/who.health.data.md
What who.health.data does on Apibase
AI agents call who.health.data 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 |
|---|---|---|---|
limit | integer | — | Number of data points to return, max 100 (default 20) |
country | string | — | ISO 3166-1 alpha-3 country code (e.g. "USA", "DEU", "BRA", "JPN"). Omit for all countries |
year_to | integer | — | Latest year to include (e.g. 2023) |
indicator | string | Yes | WHO indicator code (e.g. "WHOSIS_000001" for life expectancy, "MDG_0000000001" for under-5 mortality). Get codes from who.indicators |
year_from | integer | — | Earliest year to include (e.g. 2000) |
Parameters from the server's own tool schema.
Why who.health.data is rated Low
Tool retrieves public health statistics without modifying data or triggering external operations.
From the tool's definition Retrieve WHO health data, filtered by country and year range
Attacks that exploit this kind of access
The rule that runs who.health.data 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 who.health.data, this is the rule to start with:
who.health.data 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 who.health.data call is checked against it from then on.
Questions about who.health.data
Retrieve WHO health data for a specific indicator, optionally filtered by country and year range. Returns values for up to 194 countries spanning multiple decades. Official UN member state reporting data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
who.health.data accepts 5 parameters: limit, country, year_to, indicator, year_from. Required: indicator. 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 who.health.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 Apibase. Nothing to install.
who.health.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 who.health.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 who.health.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.
who.health.data 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