gbif.biodiversity.species_details
Get full taxonomic profile for a species by GBIF taxon key. Returns classification hierarchy, vernacular (common) names, synonyms, number of descendants, and accepted name. Source: GBIF backbone taxonomy.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gbif.biodiversity.species-details.md
What gbif.biodiversity.species_details does on Apibase
AI agents call gbif.biodiversity.species_details 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 |
|---|---|---|---|
taxon_key | integer | Yes | GBIF taxon key (numeric ID from species search results) |
Parameters from the server's own tool schema.
Why gbif.biodiversity.species_details is rated Low
Retrieves species taxonomy data from GBIF backbone with no side effects or data modification.
From the tool's definition Get full taxonomic profile, Returns classification hierarchy, vernacular names, synonyms
Attacks that exploit this kind of access
The rule that runs gbif.biodiversity.species_details 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.species_details, this is the rule to start with:
gbif.biodiversity.species_details 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.species_details call is checked against it from then on.
Questions about gbif.biodiversity.species_details
Get full taxonomic profile for a species by GBIF taxon key. Returns classification hierarchy, vernacular (common) names, synonyms, number of descendants, and accepted name. Source: GBIF backbone taxonomy. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gbif.biodiversity.species_details accepts 1 parameter: 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.species_details: 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.species_details 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.species_details 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.species_details. 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.species_details 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