gbif.biodiversity.occurrences
Search 2.5B+ species occurrence records by taxon, country, and year. Returns observation coordinates, date, collector institution, basis of record (specimen/observation). Filter by ISO country code. Source: GBIF (2000+ institutions, 100+ countries).
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gbif.biodiversity.occurrences.md
What gbif.biodiversity.occurrences does on Apibase
AI agents call gbif.biodiversity.occurrences 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 |
|---|---|---|---|
year | integer | — | Filter by observation year (e.g. 2024) |
limit | integer | — | Number of results (1-50, default 10) |
country | string | — | ISO 3166-1 alpha-2 country code (e.g. US, GB, BR, AU) |
taxon_key | integer | Yes | GBIF taxon key for the species to search occurrences |
Parameters from the server's own tool schema.
Why gbif.biodiversity.occurrences is rated Low
Query-only tool retrieving biodiversity observation data without modification or execution capabilities.
From the tool's definition Search occurrence records, returns coordinates/date/institution
Attacks that exploit this kind of access
The rule that runs gbif.biodiversity.occurrences 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 gbif.biodiversity.occurrences, this is the rule to start with:
gbif.biodiversity.occurrences 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 gbif.biodiversity.occurrences call is checked against it from then on.
Questions about gbif.biodiversity.occurrences
Search 2.5B+ species occurrence records by taxon, country, and year. Returns observation coordinates, date, collector institution, basis of record (specimen/observation). Filter by ISO country code. Source: GBIF (2000+ institutions, 100+ countries). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gbif.biodiversity.occurrences accepts 4 parameters: year, limit, country, taxon_key. Required: taxon_key. 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 gbif.biodiversity.occurrences: 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.
gbif.biodiversity.occurrences 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 gbif.biodiversity.occurrences 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 gbif.biodiversity.occurrences. 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.
gbif.biodiversity.occurrences 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