Move a page to a new parent (nesting) or root. Essential for organizing pages created via
AI agents use move_page to create or update resources in Docmost MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Docmost MCP Server environment.
Moving a page changes its organizational location and potentially its access patterns or visibility, but does not create, delete, or execute arbitrary code. This is a reversible structural modification, making it a Write-category action. Severity is medium because an agent could disorganize documentation or move sensitive pages to unexpected locations, but the change can be undone by moving the page again.
From the tool's definition Tool description states 'Move a page to a new parent (nesting) or root' and is listed among sibling tools that include create_page, update_page, and delete_page. The action modifies the hierarchical structure and metadata of a documentation page.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access move_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Docmost MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for move_page:
{
"version": "1",
"default": "deny",
"tools": {
"move_page": {
"limits": [
{
"counter": "move_page_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_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.
Free to start. No card required.
Move a page to a new parent (nesting) or root. Essential for organizing pages created via. It is categorised as a Write tool in the Docmost MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Docmost MCP Server MCP server in PolicyLayer and add a rule for move_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 Docmost MCP Server. Nothing to install.
move_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 move_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 move_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.
move_page is provided by the Docmost MCP Server MCP server (mrmartinimo/docmost-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Docmost MCP Server, 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.
11 Docmost MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.