bhl.taxonomy.name_search

SERVERApibase SOURCEapibase-mcp-client

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bhl.taxonomy.name-search.md

WHAT IT DOES

What bhl.taxonomy.name_search does on Apibase

AI agents call bhl.taxonomy.name_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
`name`	string	Yes	Scientific name to look up in BHL — full or partial Latin binomial (e.g. "Quercus robur", "Homo sapiens")

Parameters from the server's own tool schema.

RISK

Why bhl.taxonomy.name_search is rated Low

Queries taxonomic database without side effects or data modification.

From the tool's definition Search for confirmed scientific names, returns list of name strings.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bhl.taxonomy.name_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 bhl.taxonomy.name_search, this is the rule to start with:

bhl.taxonomy.name_search Allowed

bhl.taxonomy.name_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": {
    "bhl.taxonomy.name_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 bhl.taxonomy.name_search call is checked against it from then on.

FAQ

Questions about bhl.taxonomy.name_search

What does the bhl.taxonomy.name_search tool do? +

Search the Biodiversity Heritage Library for confirmed scientific (Latin) names matching a given taxonomic query. Useful for discovering historical name variants, author citations, and subspecies/variety designations for a taxon as recorded in classic natural-history literature. Returns a list of confirmed name strings in the form "Genus species Author, Year". Use bhl.literature.search with the confirmed name to find publications containing it. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does bhl.taxonomy.name_search accept? +

bhl.taxonomy.name_search accepts 1 parameter: name. Required: name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bhl.taxonomy.name_search? +

Register the Apibase MCP server in PolicyLayer and add a rule for bhl.taxonomy.name_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 bhl.taxonomy.name_search? +

bhl.taxonomy.name_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit bhl.taxonomy.name_search? +

Yes. Add a rate_limit block to the bhl.taxonomy.name_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 bhl.taxonomy.name_search completely? +

Set action: deny in the PolicyLayer policy for bhl.taxonomy.name_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 bhl.taxonomy.name_search? +

bhl.taxonomy.name_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 →