Updates properties of a Notion page. Can also update icon, cover, or archive/restore pages.
AI agents use notion_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.
This tool modifies existing Notion page content and metadata (properties, icon, cover) and can archive pages. These are Write operations—they change state reversibly without deleting data permanently. Archiving is reversible (pages can be restored), so this does not rise to Destructive.
From the tool's definition Tool description states it 'Updates properties of a Notion page. Can also update icon, cover, or archive/restore pages.' The verb 'Updates' combined with capabilities to modify page properties, icons, covers, and archive status indicates reversible data…
Attacks that exploit this kind of access
Updates properties of a Notion page. Can also update icon, cover, or archive/restore pages. 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.
Register the Notion MCP Server MCP server in PolicyLayer and add a rule for notion_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.
notion_update_page 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 notion_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.
Set action: deny in the PolicyLayer policy for notion_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.
notion_update_page is provided by the Notion MCP Server MCP server (michaelwaves/notion-mcp). 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 →