hdx.reference.organizations
List humanitarian organizations publishing data on HDX (UN agencies, NGOs, governments, clusters) with their published dataset count, optionally filtered by a name substring. Use the returned slug as the organization filter for hdx.dataset_search. Data: HDX CKAN Action API (data.humdata.org), no ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hdx.reference.organizations.md
What hdx.reference.organizations does on Apibase
AI agents call hdx.reference.organizations 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 organizations to return (1-50, default 20) |
query | string | — | Substring filter on organization title (e.g. "red cross") |
Parameters from the server's own tool schema.
Why hdx.reference.organizations is rated Low
Tool retrieves and filters organization metadata from HDX without modifying or executing operations.
From the tool's definition List humanitarian organizations publishing data; no auth required; no side effects.
Attacks that exploit this kind of access
The rule that runs hdx.reference.organizations 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.organizations, this is the rule to start with:
hdx.reference.organizations 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.organizations call is checked against it from then on.
Questions about hdx.reference.organizations
List humanitarian organizations publishing data on HDX (UN agencies, NGOs, governments, clusters) with their published dataset count, optionally filtered by a name substring. Use the returned slug as the organization 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.organizations 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.organizations: 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.organizations 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.organizations 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.organizations. 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.organizations 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