hdx.reference.locations
List countries/regions tracked on HDX with their published dataset count, optionally filtered by a name substring. Use the returned location id as the country filter for hdx.dataset_search. Data: HDX CKAN Action API (data.humdata.org), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hdx.reference.locations.md
What hdx.reference.locations does on Apibase
AI agents call hdx.reference.locations 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 | — | Max locations to return (1-100, default 50) |
query | string | — | Substring filter on location name (e.g. "sudan") |
Parameters from the server's own tool schema.
Why hdx.reference.locations is rated Low
Retrieves reference data about HDX locations with no side effects or modifications.
From the tool's definition List countries/regions, published dataset count, no auth required
Attacks that exploit this kind of access
The rule that runs hdx.reference.locations 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 hdx.reference.locations, this is the rule to start with:
hdx.reference.locations 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 hdx.reference.locations call is checked against it from then on.
Questions about hdx.reference.locations
List countries/regions tracked on HDX with their published dataset count, optionally filtered by a name substring. Use the returned location id as the country filter for hdx.dataset_search. Data: HDX CKAN Action API (data.humdata.org), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
hdx.reference.locations accepts 2 parameters: limit, query. 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 hdx.reference.locations: 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.
hdx.reference.locations 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 hdx.reference.locations 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 hdx.reference.locations. 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.
hdx.reference.locations 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