// SCAN REPORT

Personal Library MCP Server

5 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 3 Jul 2026

3 can modify or destroy data

2 read-only

5 tools total

Community server · catalogue entry verified 03/07/2026

How to control Personal Library MCP Server ↓

TOOL MAP

What Personal Library MCP Server exposes to your agents

Read (2) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Personal Library MCP Server tools

Destructive · High delete_book The tool permanently removes a book record from persistent storage with no stated undo capability. Write · Low add_book Adding a book creates a new record in the SQLite database but is fully reversible—the book entry can be deleted or corrected. Write · Low update_book_status update_book_status modifies book metadata (owned/read status) in the SQLite database, but the changes are reversible—a user can update the status again to correct any mistake.

3 of Personal Library MCP Server's 5 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Personal Library MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Personal Library MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "delete_book": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "add_book": {
    "limits": [
      {
        "counter": "add_book_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "list_books": {
    "limits": [
      {
        "counter": "list_books_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Personal Library MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON PERSONAL LIBRARY →

Instant setup, no code required.

FULL CATALOGUE

All 5 Personal Library MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_book Removes a book from the library.

WRITE 2 tools

Write add_book Adds a new book to the library. Write update_book_status Updates the owned and/or read status of a book by ISBN.

READ 2 tools

Read list_books Lists books in the library. Read search_books Searches for books by name or ISBN.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Personal Library MCP Server

Can an AI agent delete data through the Personal Library MCP Server MCP server? +

Yes. The Personal Library MCP Server server exposes 1 destructive tools including delete_book. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Personal Library MCP Server? +

The Personal Library MCP Server server has 2 write tools including add_book, update_book_status. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Personal Library MCP Server.

How many tools does the Personal Library MCP Server MCP server expose? +

5 tools across 3 categories: Destructive, Read, Write. 2 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Personal Library MCP Server? +

Register the Personal Library MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Personal Library MCP Server tool call.

Deterministic rules across all 5 Personal Library MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON PERSONAL LIBRARY →

Instant setup, no code required.

5 Personal Library MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.