Move one or more Notion pages or databases to a new parent.
AI agents use notion-move-pages to create or update resources in Notion — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Notion environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
new_parent | object | — | The new parent under which the pages will be moved. This can be a page, the workspace, a database, or a specific data source under a database when there are mul |
page_or_database_ids | array | — | An array of up to 100 page or database IDs to move. IDs are v4 UUIDs and can be supplied with or without dashes (e.g. extracted from a <page> or <database> URL |
Parameters from the server's own tool schema.
Moving pages/databases is a reversible modification operation (pages can be moved back). It alters data relationships and structure but does not create new content (not pure Create), does not execute external code (not Execute), and does not irreversibly delete anything (not Destructive).
From the tool's definition Tool performs 'Move one or more Notion pages or databases to a new parent' — this modifies the structural organization and parent relationships of pages/databases, changing their location within the hierarchy without deleting them.
Documented attack patterns abuse exactly the kind of access notion-move-pages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notion, and nothing reaches the server without passing your rules. This is the rule we recommend for notion-move-pages:
{
"version": "1",
"default": "deny",
"tools": {
"notion-move-pages": {
"limits": [
{
"counter": "notion-move-pages_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}notion-move-pages 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.
Free to start. No card required.
Move one or more Notion pages or databases to a new parent. It is categorised as a Write tool in the Notion MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
notion-move-pages accepts 2 parameters: new_parent, page_or_database_ids. The full parameter table on this page comes from the server's own tool schema.
Register the Notion MCP server in PolicyLayer and add a rule for notion-move-pages: 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. Nothing to install.
notion-move-pages 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-move-pages 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-move-pages. 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-move-pages is provided by the Notion MCP server (@notion-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notion, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
26 Notion tools catalogued and risk-classified — across an index of 43,000+ MCP servers.