unarchive_document
AI agents use unarchive_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.
Unarchiving a document modifies its metadata/status state reversibly, making it visible/accessible again. This is a Write operation (state change without deletion). Severity is medium because misuse could expose sensitive archived documents or clutter workflows, but the action is reversible.
From the tool's definition Tool name 'unarchive_document' indicates reversal of archival status; sibling tools show this server handles document state changes (archive_document, batch_archive_documents, batch_update_documents).
Attacks that exploit this kind of access
unarchive_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 unarchive_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.
unarchive_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 unarchive_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 unarchive_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.
unarchive_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 →