who.health.indicators
List 1,000+ WHO Global Health Observatory indicators: life expectancy, mortality rates, disease burden, immunization, nutrition, mental health, environmental health. Returns indicator codes for use with who.data.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/who.health.indicators.md
What who.health.indicators does on Apibase
AI agents call who.health.indicators 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 indicators to return, max 100 (default 20) |
search | string | — | Keyword to filter indicators by name (e.g. "mortality", "immunization", "life expectancy", "HIV", "malaria") |
Parameters from the server's own tool schema.
Why who.health.indicators is rated Low
Tool retrieves public health indicator metadata with no side effects or write/execute/financial capabilities.
From the tool's definition List 1,000+ indicators: life expectancy, mortality rates, disease burden, immunization, nutrition, mental health
Attacks that exploit this kind of access
The rule that runs who.health.indicators 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.indicators, this is the rule to start with:
who.health.indicators 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.indicators call is checked against it from then on.
Questions about who.health.indicators
List 1,000+ WHO Global Health Observatory indicators: life expectancy, mortality rates, disease burden, immunization, nutrition, mental health, environmental health. Returns indicator codes for use with who.data. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
who.health.indicators accepts 2 parameters: limit, search. 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.indicators: 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.indicators 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.indicators 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.indicators. 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.indicators 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