New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

hdx-hapi.food.security_ipc

Get IPC (Integrated Food Security Phase Classification) data — population counts by food-insecurity phase (1=minimal to 5=catastrophe), current and projected. Filter by location_code (ISO3), ipc_phase, admin1_name, and admin_level. Data: HDX Humanitarian API (hapi.humdata.org), run by UN OCHA Cen...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 70 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.food.security-ipc.md

What hdx-hapi.food.security_ipc does on Apibase

AI agents call hdx-hapi.food.security_ipc 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.

ParameterTypeRequiredDescription
limit integer — Maximum rows to return (1-1000, default 100)
offset integer — Number of rows to skip, for pagination (default 0)
ipc_phase string — IPC phase classification: 1=minimal, 2=stressed, 3=crisis, 4=emergency, 5=catastrophe, 3+=crisis or worse, all=all phases
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
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.

Why hdx-hapi.food.security_ipc is rated Low

Read-only query of humanitarian food security data with no side effects.

From the tool's definition Get IPC data — population counts by food-insecurity phase

Questions about hdx-hapi.food.security_ipc

What does the hdx-hapi.food.security_ipc tool do? +

Get IPC (Integrated Food Security Phase Classification) data — population counts by food-insecurity phase (1=minimal to 5=catastrophe), current and projected. Filter by location_code (ISO3), ipc_phase, 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.food.security_ipc accept? +

hdx-hapi.food.security_ipc accepts 7 parameters: limit, offset, ipc_phase, admin1_name, admin_level, 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.food.security_ipc? +

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

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

Can I rate-limit hdx-hapi.food.security_ipc? +

Yes. Add a rate_limit block to the hdx-hapi.food.security_ipc 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.food.security_ipc completely? +

Set action: deny in the PolicyLayer policy for hdx-hapi.food.security_ipc. 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.food.security_ipc? +

hdx-hapi.food.security_ipc 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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.