worms.species.vernaculars
Retrieve all registered vernacular (common) names for a marine taxon by AphiaID across all languages. Each entry includes the common name, ISO language code, and full language name. For example, AphiaID 137102 (Orcinus orca) returns "killer whale" (English), "orca" (Spanish), "épaulard" (French),...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/worms.species.vernaculars.md
What worms.species.vernaculars does on Apibase
AI agents call worms.species.vernaculars 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 |
|---|---|---|---|
aphia_id | integer | Yes | WoRMS AphiaID of the taxon whose vernacular (common) names you want — returns names across all registered languages (e.g. "killer whale" in English, "orca" in S |
Parameters from the server's own tool schema.
Why worms.species.vernaculars is rated Low
Tool queries and retrieves taxonomic data with no side effects or modifications to any system.
From the tool's definition Retrieve all registered vernacular names for marine taxon by AphiaID
Attacks that exploit this kind of access
The rule that runs worms.species.vernaculars 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 worms.species.vernaculars, this is the rule to start with:
worms.species.vernaculars 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 worms.species.vernaculars call is checked against it from then on.
Questions about worms.species.vernaculars
Retrieve all registered vernacular (common) names for a marine taxon by AphiaID across all languages. Each entry includes the common name, ISO language code, and full language name. For example, AphiaID 137102 (Orcinus orca) returns "killer whale" (English), "orca" (Spanish), "épaulard" (French), and dozens more. Useful for multilingual species identification, biodiversity apps, and natural-history content. Source: World Register of Marine Species, CC BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
worms.species.vernaculars accepts 1 parameter: aphia_id. Required: aphia_id. 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 worms.species.vernaculars: 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.
worms.species.vernaculars 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 worms.species.vernaculars 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 worms.species.vernaculars. 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.
worms.species.vernaculars 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