gbif-get-occurrence-counts
Get aggregate GBIF occurrence counts, optionally filtered by country.
This record as markdown: /tools/io-github-derekslinz-meta-data-mcp/gbif-get-occurrence-counts.md
What gbif-get-occurrence-counts does on Meta Data Mcp
AI agents call gbif-get-occurrence-counts to retrieve information from Meta Data Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why gbif-get-occurrence-counts is rated Low
This tool retrieves aggregated statistics from a public biodiversity database. It has no side effects, cannot modify or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal — an agent could at worst retrieve unwanted datasets, but cannot harm data integrity, financial systems, or external services. Classified as Read per the low-risk data retrieval category.
From the tool's definition Tool queries 'aggregate GBIF occurrence counts' with optional filtering — a retrieval operation without modification, deletion, or execution. GBIF (Global Biodiversity Information Facility) is a standard open science database.
Attacks that exploit this kind of access
The rule that runs gbif-get-occurrence-counts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Data Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gbif-get-occurrence-counts, this is the rule to start with:
gbif-get-occurrence-counts 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 Meta Data Mcp, apply this rule, and every gbif-get-occurrence-counts call is checked against it from then on.
Questions about gbif-get-occurrence-counts
Get aggregate GBIF occurrence counts, optionally filtered by country. It is categorised as a Read tool in the Meta Data Mcp MCP Server, which means it retrieves data without modifying state.
Register the Meta Data MCP server in PolicyLayer and add a rule for gbif-get-occurrence-counts: 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 Meta Data Mcp. Nothing to install.
gbif-get-occurrence-counts 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-get-occurrence-counts 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-get-occurrence-counts. 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-get-occurrence-counts is provided by the Meta Data MCP server (pypi:meta-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Data, and thousands of servers like it.
This server
Across the catalogue