update_page · Notion MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_page does on Notion MCP Server

AI agents use update_page to create or update resources in Notion MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion MCP Server environment.

WHY IT NEEDS A POLICY

Why update_page needs a policy

The tool creates or modifies data reversibly by updating Notion page properties. It does not delete data (that is delete_page's role), does not execute arbitrary code, and does not involve financial transactions.

From the tool's definition "Updates properties (fields) of a Notion page (database record)" and "You can update individual properties or multiple properties simultaneously" indicate the tool modifies existing data reversibly without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_page Rate-limited

update_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_page": {
      "limits": [
        {
          "counter": "update_page_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Notion MCP Server, so you can run agents against it safely.

FAQ

Questions about update_page

What does the update_page tool do? +

Updates properties (fields) of a Notion page (database record). Supports ALL property types: title, status, date, checkbox, number, select, multi-select, URL, email, phone number, people, relations, and more. You can update individual properties or multiple properties simultaneously. Examples: change status to. It is categorised as a Write tool in the Notion MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_page? +

Register the Notion MCP Server MCP server in PolicyLayer and add a rule for update_page: 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 Notion MCP Server. Nothing to install.

What risk level is update_page? +

update_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_page? +

Yes. Add a rate_limit block to the update_page 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.

How do I block update_page completely? +

Set action: deny in the PolicyLayer policy for update_page. 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.

What MCP server provides update_page? +

update_page is provided by the Notion MCP Server MCP server (kazy1014/notion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.