book_search
Search the full Project Gutenberg catalog (~78,500 public-domain books) live via Gutendex by title / author / subject keyword, with optional author, subject, and language filters. Ranked by keyword relevance then download popularity. Returns each book's Gutenberg id, title, author(s), language, a...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/book-search.md
What book_search does on Livedatalink
AI agents call book_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 rows to return (default 25, max 100). |
query | string | — | Title / author / subject keyword, e.g. 'frankenstein', 'sherlock holmes', 'astronomy'. |
author | string | — | Optional author-name fragment, e.g. 'Shelley', 'Twain'. |
subject | string | — | Optional subject fragment, e.g. 'Science fiction', 'Detective'. |
language | string | — | Optional language code filter, e.g. 'en', 'fr'. |
Parameters from the server's own tool schema.
Why book_search is rated Low
Even though book_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs book_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_search, this is the rule to start with:
book_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_search call is checked against it from then on.
Questions about book_search
Search the full Project Gutenberg catalog (~78,500 public-domain books) live via Gutendex by title / author / subject keyword, with optional author, subject, and language filters. Ranked by keyword relevance then download popularity. Returns each book's Gutenberg id, title, author(s), language, and download count. Use book_fulltext_search to search inside the locally indexed top books. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
book_search accepts 5 parameters: limit, query, author, subject, language. 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_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_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_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_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_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