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

malaria-atlas.epidemiology.case_estimates

Get modeled confirmed malaria case counts (P. falciparum or P. vivax) per admin1 region (state/province) and year for a country, covering 1980-2017, alongside total population for that region/year. Use malaria-atlas.country_list first to find a valid ISO3 country code. Data: Malaria Atlas Project...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 42 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/malaria-atlas.epidemiology.case-estimates.md

What malaria-atlas.epidemiology.case_estimates does on Apibase

AI agents call malaria-atlas.epidemiology.case_estimates 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
year integer — Filter to a single calendar year (1980-2017). Omit to return all available years.
limit integer — Maximum number of admin1-region/year rows to return (1-500). Defaults to 50.
country string Yes ISO3166 alpha-3 country code to get confirmed case estimates for (e.g. "IDN").
species string Yes Malaria parasite species: "pf" (Plasmodium falciparum) or "pv" (Plasmodium vivax).

Parameters from the server's own tool schema.

Why malaria-atlas.epidemiology.case_estimates is rated Low

Retrieves epidemiological data with no side effects or mutations to any system.

From the tool's definition Get modeled confirmed malaria case counts per admin1 region and year for a country

Questions about malaria-atlas.epidemiology.case_estimates

What does the malaria-atlas.epidemiology.case_estimates tool do? +

Get modeled confirmed malaria case counts (P. falciparum or P. vivax) per admin1 region (state/province) and year for a country, covering 1980-2017, alongside total population for that region/year. Use malaria-atlas.country_list first to find a valid ISO3 country code. Data: Malaria Atlas Project GeoServer WFS (data.malariaatlas.org), 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 malaria-atlas.epidemiology.case_estimates accept? +

malaria-atlas.epidemiology.case_estimates accepts 4 parameters: year, limit, country, species. Required: country, species. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on malaria-atlas.epidemiology.case_estimates? +

Register the Apibase MCP server in PolicyLayer and add a rule for malaria-atlas.epidemiology.case_estimates: 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 malaria-atlas.epidemiology.case_estimates? +

malaria-atlas.epidemiology.case_estimates is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit malaria-atlas.epidemiology.case_estimates? +

Yes. Add a rate_limit block to the malaria-atlas.epidemiology.case_estimates 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 malaria-atlas.epidemiology.case_estimates completely? +

Set action: deny in the PolicyLayer policy for malaria-atlas.epidemiology.case_estimates. 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 malaria-atlas.epidemiology.case_estimates? +

malaria-atlas.epidemiology.case_estimates 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.