Adds a new book to the library.
AI agents use add_book to create or update resources in Personal Library MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Library MCP Server environment.
Adding a book creates a new record in the SQLite database but is fully reversible—the book entry can be deleted or corrected. This is a straightforward data creation operation with no side effects beyond the database modification itself. Severity is low because misuse would only add unwanted entries to a personal reading list, causing no financial, security, or system damage.
From the tool's definition Tool description states it 'Adds a new book to the library.' The sibling tools include delete_book (destructive), list_books (read), search_books (read), and update_book_status (write), confirming this is a write operation that creates new data reversibly.
Attacks that exploit this kind of access
Adds a new book to the library. It is categorised as a Write tool in the Personal Library MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Library MCP Server MCP server in PolicyLayer and add a rule for add_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 Personal Library MCP Server. Nothing to install.
add_book is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_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 add_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.
add_book is provided by the Personal Library MCP Server MCP server (srgsanky/mcp-demo). 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 →