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

obis.marine.checklist

Generate a species checklist from OBIS occurrence data for a given taxon group or geographic area. Returns a ranked list of species with occurrence record counts, full taxonomy (phylum/class/order/family/genus), WoRMS AphiaID, and marine/brackish habitat flags. Filter by parent taxon (e.g. "Mollu...

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

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/obis.marine.checklist.md

What obis.marine.checklist does on Apibase

AI agents call obis.marine.checklist 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
limit integer — Number of species in the checklist to return (1-100, default 20).
areaid integer — OBIS area ID to restrict checklist to a geographic region. Use area search to find IDs.
taxonid integer — WoRMS AphiaID to filter checklist by taxon. Alternative to scientificname for precise filtering.
marine_only boolean — If true (default), restricts results to marine-only species. Set false to include brackish/coastal taxa.
scientificname string — Scientific name filter — restricts checklist to a taxon and its descendants (e.g. "Mollusca" for all molluscs).

Parameters from the server's own tool schema.

Why obis.marine.checklist is rated Low

Retrieves and queries publicly available marine biodiversity data without side effects.

From the tool's definition Generate checklist from occurrence data, returns ranked species list with taxonomy.

Questions about obis.marine.checklist

What does the obis.marine.checklist tool do? +

Generate a species checklist from OBIS occurrence data for a given taxon group or geographic area. Returns a ranked list of species with occurrence record counts, full taxonomy (phylum/class/order/family/genus), WoRMS AphiaID, and marine/brackish habitat flags. Filter by parent taxon (e.g. "Mollusca" for all molluscs), WoRMS AphiaID, or OBIS area ID. Useful for biodiversity assessments, EIA surveys, and species inventories. Source: OBIS — free, CC BY 4.0, 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 obis.marine.checklist accept? +

obis.marine.checklist accepts 5 parameters: limit, areaid, taxonid, marine_only, scientificname. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on obis.marine.checklist? +

Register the Apibase MCP server in PolicyLayer and add a rule for obis.marine.checklist: 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 obis.marine.checklist? +

obis.marine.checklist is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit obis.marine.checklist? +

Yes. Add a rate_limit block to the obis.marine.checklist 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 obis.marine.checklist completely? +

Set action: deny in the PolicyLayer policy for obis.marine.checklist. 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 obis.marine.checklist? +

obis.marine.checklist 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.