book_details
Get full catalog metadata for a single book by its Project Gutenberg id (title, authors, subjects, languages, copyright, download count, and whether its full text is indexed here).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/book-details.md
What book_details does on Livedatalink
AI agents call book_details 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 |
|---|---|---|---|
gutenberg_id | number | Yes | Project Gutenberg ebook id, e.g. 84 (Frankenstein). |
Parameters from the server's own tool schema.
Why book_details is rated Low
This tool queries a catalog database to return metadata about a book. It does not create, modify, delete, or execute any actions—it simply retrieves and returns existing information. There is no financial transaction, no code execution, and no destructive operation.
From the tool's definition Tool retrieves 'full catalog metadata for a single book' including 'title, authors, subjects, languages, copyright, download count'.
Attacks that exploit this kind of access
The rule that runs book_details 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_details, this is the rule to start with:
book_details 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_details call is checked against it from then on.
Questions about book_details
Get full catalog metadata for a single book by its Project Gutenberg id (title, authors, subjects, languages, copyright, download count, and whether its full text is indexed here). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
book_details accepts 1 parameter: gutenberg_id. Required: gutenberg_id. 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_details: 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_details 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_details 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_details. 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_details 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