who.health.indicator_search
Search the WHO Global Health Observatory catalog of 3,000+ health indicators by keyword. Returns indicator codes, full names, and definitions for topics like immunization, life expectancy, mortality, tuberculosis, malaria, maternal health, NCDs, and SDG health metrics. Use the returned indicator_...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/who.health.indicator-search.md
What who.health.indicator_search does on Apibase
AI agents call who.health.indicator_search 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 | — | Maximum number of indicators to return (1–100, default 20). |
keyword | string | — | Keyword to search indicator names (e.g. "immunization", "mortality", "tuberculosis"). Omit to list all indicators. |
Parameters from the server's own tool schema.
Why who.health.indicator_search is rated Low
Retrieves publicly available WHO health indicator metadata without modifying data or executing operations.
From the tool's definition Search...catalog...Returns indicator codes, names, definitions. No side effects.
Attacks that exploit this kind of access
The rule that runs who.health.indicator_search 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_search, this is the rule to start with:
who.health.indicator_search 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_search call is checked against it from then on.
Questions about who.health.indicator_search
Search the WHO Global Health Observatory catalog of 3,000+ health indicators by keyword. Returns indicator codes, full names, and definitions for topics like immunization, life expectancy, mortality, tuberculosis, malaria, maternal health, NCDs, and SDG health metrics. Use the returned indicator_code with who.indicator_data to retrieve actual values. No auth — WHO CC BY-NC-SA 3.0 IGO, 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_search accepts 2 parameters: limit, keyword. 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_search: 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_search 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_search 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_search. 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_search 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