hdx-hapi.coordination.operational_presence

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 80 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/hdx-hapi.coordination.operational-presence.md

WHAT IT DOES

What hdx-hapi.coordination.operational_presence does on Apibase

AI agents call hdx-hapi.coordination.operational_presence 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 rows to return (1-1000, default 100)
`offset`	integer	—	Number of rows to skip, for pagination (default 0)
`org_name`	string	—	Responding organization name to filter results, e.g. "UNICEF"
`admin1_name`	string	—	1st-level subnational admin area name to filter results, e.g. "Kayes"
`admin_level`	string	—	Admin granularity of returned rows: 0=national, 1=admin1, 2=admin2
`sector_name`	string	—	Humanitarian sector name to filter results, e.g. "Health", "Nutrition"
`location_code`	string	—	ISO3 country code to filter results, e.g. "MLI", "AFG", "SOM"
`location_name`	string	—	Country name to filter results (alternative to location_code), e.g. "Mali"

Parameters from the server's own tool schema.

RISK

Why hdx-hapi.coordination.operational_presence is rated Low

Read-only query of public humanitarian coordination data, no side effects.

From the tool's definition Get 'who's doing what, where' humanitarian response data

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs hdx-hapi.coordination.operational_presence 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-hapi.coordination.operational_presence, this is the rule to start with:

hdx-hapi.coordination.operational_presence Allowed

hdx-hapi.coordination.operational_presence is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "hdx-hapi.coordination.operational_presence": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every hdx-hapi.coordination.operational_presence call is checked against it from then on.

FAQ

Questions about hdx-hapi.coordination.operational_presence

What does the hdx-hapi.coordination.operational_presence tool do? +

Get "who's doing what, where" (3W) humanitarian response data — which organizations are active in which sector (Health, Nutrition, WASH, etc.) and location. Filter by location_code (ISO3), sector_name, org_name, admin1_name, and admin_level. Data: HDX Humanitarian API (hapi.humdata.org), run by UN OCHA Centre for Humanitarian Data, CC BY 4.0, no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does hdx-hapi.coordination.operational_presence accept? +

hdx-hapi.coordination.operational_presence accepts 8 parameters: limit, offset, org_name, admin1_name, admin_level, sector_name, location_code, location_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on hdx-hapi.coordination.operational_presence? +

Register the Apibase MCP server in PolicyLayer and add a rule for hdx-hapi.coordination.operational_presence: 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.

What risk level is hdx-hapi.coordination.operational_presence? +

hdx-hapi.coordination.operational_presence is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit hdx-hapi.coordination.operational_presence? +

Yes. Add a rate_limit block to the hdx-hapi.coordination.operational_presence 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.

How do I block hdx-hapi.coordination.operational_presence completely? +

Set action: deny in the PolicyLayer policy for hdx-hapi.coordination.operational_presence. 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.

What MCP server provides hdx-hapi.coordination.operational_presence? +

hdx-hapi.coordination.operational_presence 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.

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →