AI agents use wiki_move_page to create or update resources in Wiki Js — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wiki Js environment.
Moving or renaming a page is a reversible write operation that changes metadata (path/title) but preserves the underlying content. It can be undone by moving the page back. While it has broader impact than a simple update (affecting navigation, links, and references), it does not meet the threshold for Destructive (which requires irreversibility) nor Execute (which requires code/command execution).
From the tool's definition Tool name and description explicitly state 'Move/rename a wiki page to a new path.' This modifies the location and identity of an existing page but does not delete data or create new independent copies.
Attacks that exploit this kind of access
Move/rename a wiki page to a new path. It is categorised as a Write tool in the Wiki Js MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wiki Js MCP server in PolicyLayer and add a rule for wiki_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 Wiki Js. Nothing to install.
wiki_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 wiki_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 wiki_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.
wiki_move_page is provided by the Wiki Js MCP server (osianet/wiki-js-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 →