AI agents call search_books to retrieve information from Weread without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
keyword | string | Yes | Search keyword to match book title, author, translator or category |
exact_match | boolean | — | Whether to use exact matching, default is fuzzy matching |
max_results | integer | — | Maximum number of results to return |
include_details | boolean | — | Whether to include detailed information |
Parameters from the server's own tool schema.
The tool searches and returns book data without creating, modifying, deleting, or executing any operations. It is purely informational, querying the user's existing bookshelf data. This is a standard Read category operation with minimal security risk.
From the tool's definition Tool name is 'search_books' and description states it 'Search for books in the user's bookshelf by keywords and return matching books with details and reading progress' — this is a retrieval/query operation with no side effects.
Attacks that exploit this kind of access
Search for books in the user's bookshelf by keywords and return matching books with details and reading progress. It is categorised as a Read tool in the Weread MCP Server, which means it retrieves data without modifying state.
search_books accepts 4 parameters: keyword, exact_match, max_results, include_details. Required: keyword. The full parameter table on this page comes from the server's own tool schema.
Register the Weread MCP server in PolicyLayer and add a rule for search_books: 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 Weread. Nothing to install.
search_books 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_books 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_books. 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_books is provided by the Weread MCP server (mcp-server-weread). 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 →