obis.marine.occurrence_search

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 80 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.occurrence-search.md

WHAT IT DOES

What obis.marine.occurrence_search does on Apibase

AI agents call obis.marine.occurrence_search 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
`lat`	number	—	Center latitude for geographic search (decimal degrees, -90 to 90). Requires lon and radius.
`lon`	number	—	Center longitude for geographic search (decimal degrees, -180 to 180). Requires lat and radius.
`limit`	integer	—	Number of occurrence records to return (1-100, default 10).
`radius`	number	—	Search radius in kilometers around the lat/lon center point. Requires lat and lon.
`maxyear`	integer	—	Latest observation year to include (e.g. 2024). Pairs with minyear.
`minyear`	integer	—	Earliest observation year to include (e.g. 2000). Pairs with maxyear.
`taxonid`	integer	—	WoRMS AphiaID (numeric taxon identifier). Use instead of or alongside scientificname for precise lookups.
`scientificname`	string	—	Scientific name of the marine species to search (e.g. "Abra alba", "Gadus morhua", "Thunnus thynnus"). Supports partial matching.

Parameters from the server's own tool schema.

RISK

Why obis.marine.occurrence_search is rated Low

Tool retrieves biodiversity observation data with no side effects, modifications, or access to sensitive systems.

From the tool's definition Search 100M+ marine species occurrence records. Filter by scientific name, geographic coordinates, year range.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs obis.marine.occurrence_search 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 obis.marine.occurrence_search, this is the rule to start with:

obis.marine.occurrence_search Allowed

obis.marine.occurrence_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "obis.marine.occurrence_search": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every obis.marine.occurrence_search call is checked against it from then on.

FAQ

Questions about obis.marine.occurrence_search

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

Search 100M+ marine species occurrence records in the Ocean Biodiversity Information System (OBIS). Filter by scientific name, WoRMS AphiaID, geographic coordinates with radius, or year range. Each record includes GPS coordinates, observation year, depth, sea-surface temperature, dataset source, and full taxonomic classification (kingdom→species). Covers all ocean environments: pelagic, benthic, coastal, deep-sea. 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.occurrence_search accept? +

obis.marine.occurrence_search accepts 8 parameters: lat, lon, limit, radius, maxyear, minyear, taxonid, 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.occurrence_search? +

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

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

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

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

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

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

KEEP EXPLORING

More on Apibase, and thousands of servers like it.

This server

All 1384 Apibase tools →

Across the catalogue

evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →