// SCAN REPORT

Notion API MCP Server

17 tools. 9 can modify or destroy data without limits.

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

Last updated: 11 Jun 2026

9 can modify or destroy data

8 read-only

17 tools total

Community server · catalogue entry verified 11/06/2026

How to control Notion API MCP Server ↓

TOOL MAP

What Notion API MCP Server exposes to your agents

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

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Notion API MCP Server tools

Destructive · High delete_block Deletion of blocks is a destructive operation that permanently removes data. Write · Medium add_content_blocks This tool creates or modifies content blocks within Notion pages, which is a reversible Write operation. Write · Medium add_todo This tool creates new todo items in Notion, which is a reversible write operation. Write · Medium archive_page Archiving is a state change (Write category) rather than permanent deletion (Destructive).

9 of Notion API MCP Server's 17 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Notion API MCP Server

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

Deny destructive operations

{
  "delete_block": {
    "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_content_blocks": {
    "limits": [
      {
        "counter": "add_content_blocks_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "get_block_content": {
    "limits": [
      {
        "counter": "get_block_content_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 Notion API 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 NOTION API →

Free to start. No card required.

FULL CATALOGUE

All 17 Notion API MCP Server tools

DESTRUCTIVE 1 tools

Destructive delete_block Delete blocks

WRITE 8 tools

Write add_content_blocks Add content blocks with positioning support Write add_todo Add a new todo with rich features Write archive_page Archive a Notion page Write create_database Create a new database with custom schema in a parent page Write create_page Create a new page in Notion Write restore_page Restore an archived Notion page Write update_block_content Update a block Write update_page Update a Notion page

READ 8 tools

Read get_block_content Get content of a specific block by its ID Read get_database_info Get information about the configured database Read get_page Retrieve a Notion page by its ID Read get_page_property Get a page property item Read list_block_children List all children of a block Read query_database Query database with filters and sorting Read search_todos Search todos with advanced filtering Read verify_connection Verify authentication with Notion API

EXPLORE

Related servers

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

FAQ

Questions about Notion API MCP Server

Can an AI agent delete data through the Notion API MCP Server MCP server? +

Yes. The Notion API MCP Server server exposes 1 destructive tools including delete_block. 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 Notion API MCP Server? +

The Notion API MCP Server server has 8 write tools including add_content_blocks, add_todo, archive_page. 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 Notion API MCP Server.

How many tools does the Notion API MCP Server MCP server expose? +

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

How do I enforce a policy on Notion API MCP Server? +

Register the Notion API 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 Notion API MCP Server tool call.

Deterministic rules across all 17 Notion API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON NOTION API →

Free to start. No card required.

17 Notion API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.