// SCAN REPORT

Hardcover

29 tools. 14 can modify or destroy data without limits.

5 destructive tools with no built-in limits. Policy required.

Last updated: 29 Jun 2026

14 can modify or destroy data

15 read-only

29 tools total

Community server · catalogue entry verified 29/06/2026

How to control Hardcover ↓

TOOL MAP

What Hardcover exposes to your agents

Read (15) Write / Execute (9) Destructive / Financial (5)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Hardcover tools

Destructive · High delete_journal_entry This tool permanently removes user data (journal entries) with no indicated undo or recovery mechanism. Destructive · High delete_list This tool permanently removes a user's list from the Hardcover library with no recovery option. Destructive · High delete_user_book This tool permanently deletes a user's book record from their library with no recovery option. Destructive · Medium delete_user_book_read The tool permanently removes a reading date entry with no undo capability.

14 of Hardcover's 29 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Hardcover

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

Deny destructive operations

{
  "delete_journal_entry": {
    "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_to_list": {
    "limits": [
      {
        "counter": "add_book_to_list_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_author": {
    "limits": [
      {
        "counter": "get_author_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 Hardcover — 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 HARDCOVER →

Instant setup, no code required.

FULL CATALOGUE

All 29 Hardcover tools

DESTRUCTIVE 5 tools

Destructive delete_journal_entry Delete a reading journal entry by ID. Destructive delete_list Delete a Hardcover list by ID. This cannot be undone. Destructive delete_user_book Remove a book from your library entirely. This cannot be undone. Destructive delete_user_book_read Delete a reading date entry by its ID. This cannot be undone. Destructive remove_book_from_list Remove a book from a list. Use id or list_id + book_id.

WRITE 9 tools

Write add_book_to_list Add a book to a Hardcover list. Write add_journal_entry Create a reading journal entry (for example a note or quote) for a book. Write add_user_book_read Add a reading date or progress entry. Updates active read if one exists. Write create_list Create a new Hardcover list. Write set_edition_owned Mark an edition as owned or not owned. Write set_reading_goal Create or update a reading goal with target, metric, dates, and optional Write set_user_book Set a book Write update_list Update an existing Hardcover list Write update_user_book_read Update a reading date or progress entry. Preserves unspecified fields.

READ 15 tools

Read get_author Get an author Read get_book Get detailed info about a specific book by its Hardcover ID or slug. Read get_edition Get edition details by Hardcover ID, ISBN-13, or ASIN. Read get_list Get a specific Hardcover list with its books by list ID. Read get_my_lists Get your Hardcover lists. Returns id, name, books count, privacy. Read get_owned_books List all books you have marked as owned. Read get_reading_goal Get your active reading goals with target, metric, progress, and date range. Read get_reading_journal Fetch reading journal entries for the authenticated user. Read get_reading_stats Get library reading statistics: total books, books per status, Read get_series Get a book series by id, slug, or name with books in reading order. Read get_user_book Get your library entry for a book: status, rating, reads. Read get_user_library Get books from your library. Filter by reading status or finished-date range Read get_user_reviews List your reviews, newest first. Includes review text, rating, and book info. Read me Get authenticated user info (id, username, name, books count). Read search_books Search Hardcover by title, author, or ISBN. Supports multiple entity types:

EXPLORE

Related servers

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

FAQ

Questions about Hardcover

Can an AI agent delete data through the Hardcover MCP server? +

Yes. The Hardcover server exposes 5 destructive tools including delete_journal_entry, delete_list, delete_user_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 Hardcover? +

The Hardcover server has 9 write tools including add_book_to_list, add_journal_entry, add_user_book_read. 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 Hardcover.

How many tools does the Hardcover MCP server expose? +

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

How do I enforce a policy on Hardcover? +

Register the Hardcover 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 Hardcover tool call.

Deterministic rules across all 29 Hardcover tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON HARDCOVER →

Instant setup, no code required.

29 Hardcover tools catalogued and risk-classified — across an index of 43,000+ MCP servers.