who.health.countries
List all 194 WHO member countries and territories with codes and names. Use returned country codes with who.data to filter health indicators by country.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/who.health.countries.md
What who.health.countries does on Apibase
AI agents call who.health.countries 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 countries to return, max 200 (default 50) |
search | string | — | Partial country name to filter (e.g. "United", "Germany", "Brazil") |
Parameters from the server's own tool schema.
Why who.health.countries is rated Low
Tool retrieves static reference data without side effects or external operations.
From the tool's definition List all 194 WHO member countries and territories with codes and names.
Attacks that exploit this kind of access
The rule that runs who.health.countries 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.countries, this is the rule to start with:
who.health.countries 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.countries call is checked against it from then on.
Questions about who.health.countries
List all 194 WHO member countries and territories with codes and names. Use returned country codes with who.data to filter health indicators by country. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
who.health.countries 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.countries: 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.countries 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.countries 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.countries. 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.countries 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