malaria-atlas.entomology.vector_occurrence
Search Anopheles mosquito vector-occurrence records: collection site, survey period, species identification, and sampling method, optionally filtered by country and/or a species-name substring (e.g. "gambiae"). Data: Malaria Atlas Project GeoServer WFS (data.malariaatlas.org), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/malaria-atlas.entomology.vector-occurrence.md
What malaria-atlas.entomology.vector_occurrence does on Apibase
AI agents call malaria-atlas.entomology.vector_occurrence 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 number of vector occurrence records to return (1-200). Defaults to 50. |
country | string | — | ISO3166 alpha-3 country code to filter mosquito vector records (e.g. "SDN"). |
species | string | — | Case-insensitive substring match on the Anopheles species name (e.g. "gambiae", "arabiensis"). |
Parameters from the server's own tool schema.
Why malaria-atlas.entomology.vector_occurrence is rated Low
Tool queries epidemiological survey data without modification, deletion, or financial impact.
From the tool's definition Search Anopheles mosquito vector-occurrence records; no auth required; retrieves data
Attacks that exploit this kind of access
The rule that runs malaria-atlas.entomology.vector_occurrence 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 malaria-atlas.entomology.vector_occurrence, this is the rule to start with:
malaria-atlas.entomology.vector_occurrence 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 malaria-atlas.entomology.vector_occurrence call is checked against it from then on.
Questions about malaria-atlas.entomology.vector_occurrence
Search Anopheles mosquito vector-occurrence records: collection site, survey period, species identification, and sampling method, optionally filtered by country and/or a species-name substring (e.g. "gambiae"). 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.
malaria-atlas.entomology.vector_occurrence accepts 3 parameters: limit, country, species. 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 malaria-atlas.entomology.vector_occurrence: 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.
malaria-atlas.entomology.vector_occurrence 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 malaria-atlas.entomology.vector_occurrence 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 malaria-atlas.entomology.vector_occurrence. 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.
malaria-atlas.entomology.vector_occurrence 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