book_fulltext_search
Search INSIDE the indexed corpus of top public-domain books for a phrase or keywords and get back the matching passages, each with the book title, author, and a snippet around the match. This is the headline feature: agents can find where a passage appears across great books. Optionally restrict ...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/book-fulltext-search.md
What book_fulltext_search does on Livedatalink
AI agents call book_fulltext_search to retrieve information from Livedatalink 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 |
|---|---|---|---|
limit | number | — | Maximum passages to return (default 10, max 50). |
query | string | Yes | Phrase or keywords to find inside the books, e.g. 'it was the best of times', 'whale'. |
gutenberg_id | number | — | Optional: restrict the search to a single indexed book by its Gutenberg id. |
Parameters from the server's own tool schema.
Why book_fulltext_search is rated Low
This tool queries an indexed corpus of public-domain books and returns matching passages. It performs a read-only search operation with no side effects—no data is created, modified, deleted, or executed. The blast radius of misuse is minimal; an agent might retrieve irrelevant passages but cannot damage systems or data. Public-domain book content poses no financial or destructive risk.
From the tool's definition Tool name is 'book_fulltext_search' and description states it 'Search[es]' a corpus and 'get[s] back the matching passages' with no mention of modification, deletion, or execution capabilities. The verb is 'search'—a retrieval operation.
Attacks that exploit this kind of access
The rule that runs book_fulltext_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For book_fulltext_search, this is the rule to start with:
book_fulltext_search 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 Livedatalink, apply this rule, and every book_fulltext_search call is checked against it from then on.
Questions about book_fulltext_search
Search INSIDE the indexed corpus of top public-domain books for a phrase or keywords and get back the matching passages, each with the book title, author, and a snippet around the match. This is the headline feature: agents can find where a passage appears across great books. Optionally restrict to one book by gutenberg_id. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
book_fulltext_search accepts 3 parameters: limit, query, gutenberg_id. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for book_fulltext_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 Livedatalink. Nothing to install.
book_fulltext_search 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 book_fulltext_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.
Set action: deny in the PolicyLayer policy for book_fulltext_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.
book_fulltext_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue