Renames a wiki page, moving it — and by default its talk page — to a new title, and returns the old and new titles plus whether a redirect was left behind. By default leaves a redirect at the old title; set leaveRedirect=false to suppress it (requires the suppressredirect right, otherwise the red...
AI agents use move-page to create or update resources in MediaWiki MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MediaWiki MCP Server environment.
move-page creates or modifies data reversibly: it renames pages and optionally leaves redirects. The operation is Write-category because: (1) it modifies page state and metadata, (2) the effects are reversible (pages can be moved back, redirects can be edited/removed), and (3) it does not irreversibly delete data or execute arbitrary code.
From the tool's definition Tool description states it "Renames a wiki page, moving it — and by default its talk page — to a new title" and can "suppress" the redirect by setting leaveRedirect=false. This is a reversible modification operation that changes page metadata and structure.
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 MediaWiki 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.
Renames a wiki page, moving it — and by default its talk page — to a new title, and returns the old and new titles plus whether a redirect was left behind. By default leaves a redirect at the old title; set leaveRedirect=false to suppress it (requires the suppressredirect right, otherwise the redirect is left regardless). Fails if the source page does not exist, if the target title already exists (unless it is a redirect and ignoreWarnings is set), or if the authenticated user lacks the move permission. Moving a File page additionally requires the file-move permission. It is categorised as a Write tool in the MediaWiki MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MediaWiki 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 MediaWiki 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 MediaWiki MCP Server MCP server (@professional-wiki/mediawiki-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MediaWiki 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.
38 MediaWiki MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.