Create a child page under another page from blocks or Markdown.
AI agents use create_page to create or update resources in Notion Private Api — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion Private Api environment.
This tool creates new pages in Notion, which is a reversible write operation. While not destructive (pages can be deleted), the severity is high because the server grants unrestricted access to an entire workspace without per-page sharing restrictions, meaning an agent could create unlimited pages across sensitive areas.
From the tool's definition Tool description states 'Create a child page' and the server description indicates 'full read/write access to the entire workspace' via an unofficial private API that bypasses standard integration controls.
Attacks that exploit this kind of access
Create a child page under another page from blocks or Markdown. It is categorised as a Write tool in the Notion Private Api MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Notion Private Api MCP server in PolicyLayer and add a rule for create_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 Private Api. Nothing to install.
create_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 create_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 create_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.
create_page is provided by the Notion Private Api MCP server (kirvigen/notion-private-api-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 →