bhl.literature.fulltext
Search within the digitized full text of Biodiversity Heritage Library publications for a specific term or phrase. Unlike the catalog search, full-text search scans the OCR-transcribed content of scanned pages, making it possible to find publications that mention a specific organism, location, co...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/bhl.literature.fulltext.md
What bhl.literature.fulltext does on Apibase
AI agents call bhl.literature.fulltext 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1) |
limit | integer | — | Number of results per page (1–50, default 10) |
query | string | Yes | Term or phrase to search within the digitized full text of BHL publications (e.g. "symbiosis nitrogen fixation") |
Parameters from the server's own tool schema.
Why bhl.literature.fulltext is rated Low
Tool performs read-only search within published literature with no data modification or execution capabilities.
From the tool's definition Search within digitized full text of Biodiversity Heritage Library publications
Attacks that exploit this kind of access
The rule that runs bhl.literature.fulltext 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.literature.fulltext, this is the rule to start with:
bhl.literature.fulltext 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 bhl.literature.fulltext call is checked against it from then on.
Questions about bhl.literature.fulltext
Search within the digitized full text of Biodiversity Heritage Library publications for a specific term or phrase. Unlike the catalog search, full-text search scans the OCR-transcribed content of scanned pages, making it possible to find publications that mention a specific organism, location, concept, or measurement even when the keyword does not appear in title or subject metadata. Returns matching publications with title, authors, publisher, date, and direct BHL URLs. Use bhl.literature.search for faster metadata-only catalog queries. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
bhl.literature.fulltext accepts 3 parameters: page, limit, query. Required: query. 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 bhl.literature.fulltext: 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.
bhl.literature.fulltext 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 bhl.literature.fulltext 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 bhl.literature.fulltext. 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.
bhl.literature.fulltext 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