full_text_search_book
AI agents call full_text_search_book to retrieve information from Neolibrarian MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Full-text search operations retrieve and query data without creating, modifying, or deleting content. The server is explicitly described as read-only, and the tool name indicates search semantics. This is a Read operation with minimal blast radius—an AI agent misusing this would only retrieve unwanted information, not alter or destroy data.
From the tool's definition Tool name 'full_text_search_book' combined with server description stating 'Enables read-only access' and 'supports full-text search'. Sibling tools include 'full_text_search' which confirms this is a search capability.
Attacks that exploit this kind of access
full_text_search_book. It is categorised as a Read tool in the Neolibrarian MCP MCP Server, which means it retrieves data without modifying state.
Register the Neolibrarian MCP server in PolicyLayer and add a rule for full_text_search_book: 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 Neolibrarian MCP. Nothing to install.
full_text_search_book 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 full_text_search_book 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 full_text_search_book. 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.
full_text_search_book is provided by the Neolibrarian MCP server (pshap/mcp-neolibrarian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →