move_document
AI agents use move_document to create or update resources in Outline MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Outline MCP Server environment.
Moving a document changes its organizational state (collection, folder, or position) reversibly. This is a Write operation—it modifies data structure without deleting content or executing arbitrary code. Severity is medium because moving documents could disrupt workflows or hide information, but the action is reversible and does not permanently destroy data or execute external code.
From the tool's definition Tool name 'move_document' indicates it modifies document location/organization within Outline. The server description mentions 'document search, reading, and management,' and sibling tools include 'batch_move_documents,' confirming move operations are part of…
Attacks that exploit this kind of access
move_document. It is categorised as a Write tool in the Outline MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Outline MCP Server MCP server in PolicyLayer and add a rule for move_document: 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 Outline MCP Server. Nothing to install.
move_document 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_document 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_document. 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_document is provided by the Outline MCP Server MCP server (mcp-outline). 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 →