search_library
AI agents call search_library 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.
The tool searches a local Calibre library, which is a query/retrieval operation with no data modification, deletion, or execution capabilities. The server is explicitly read-only. Confidence reduced slightly (0.85 vs higher) due to empty tool description, but context from server purpose and sibling tools strongly indicates Read category.
From the tool's definition Tool name 'search_library' combined with server description stating 'read-only access' and 'searching metadata' indicates retrieval functionality. Sibling tools include 'full_text_search', 'get_book_details', 'get_books_batch'—all Read operations.
Attacks that exploit this kind of access
search_library. 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 search_library: 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.
search_library 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 search_library 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 search_library. 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.
search_library 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 →