who.health.indicator_data
Retrieve time-series values for a specific WHO Global Health Observatory indicator. Filter by country (ISO alpha-3), year range, and sex (both sexes, male, or female). Returns numeric values with confidence intervals for indicators such as life expectancy at birth (WHOSIS_000001), DTP3 immunizati...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/who.health.indicator-data.md
What who.health.indicator_data does on Apibase
AI agents call who.health.indicator_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 |
|---|---|---|---|
sex | string | — | Sex dimension filter: SEX_BTSX (both sexes), SEX_MLE (male), SEX_FMLE (female). |
limit | integer | — | Maximum number of data points to return (1–100, default 20). |
year_to | integer | — | End year for time series data (inclusive, e.g. 2023). |
year_from | integer | — | Start year for time series data (inclusive, e.g. 2015). |
country_code | string | — | ISO 3166-1 alpha-3 country code to filter results (e.g. "USA", "FRA", "IND"). |
indicator_code | string | Yes | WHO GHO indicator code (e.g. "WHOSIS_000001" for life expectancy, "dptv" for DTP3 immunization, "MORT_100" for mortality). Use who.indicator_search to find code |
Parameters from the server's own tool schema.
Why who.health.indicator_data is rated Low
Retrieves historical health data with no side effects or modification capabilities.
From the tool's definition Retrieve time-series values for a specific WHO Global Health Observatory indicator
Attacks that exploit this kind of access
The rule that runs who.health.indicator_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.indicator_data, this is the rule to start with:
who.health.indicator_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.indicator_data call is checked against it from then on.
Questions about who.health.indicator_data
Retrieve time-series values for a specific WHO Global Health Observatory indicator. Filter by country (ISO alpha-3), year range, and sex (both sexes, male, or female). Returns numeric values with confidence intervals for indicators such as life expectancy at birth (WHOSIS_000001), DTP3 immunization coverage (dptv), TB incidence (MDG_0000000020), and 3,000+ more. Use who.indicator_search to find indicator codes. No auth — unlimited free. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
who.health.indicator_data accepts 6 parameters: sex, limit, year_to, year_from, country_code, indicator_code. Required: indicator_code. 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.indicator_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.indicator_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.indicator_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.indicator_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.indicator_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