edit_document
AI agents use edit_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.
The tool edits documents, which creates or modifies data reversibly. This is a Write operation—it changes document content but does not destroy data (unlike delete/archive) or move money. Severity is medium because editing documents could overwrite important information, but the action is typically reversible through version history or undo functionality common in document management systems like Outline.
From the tool's definition Tool name is 'edit_document' which indicates document modification. Server context shows document management capabilities including create_document, update_documents, and archive operations.
Attacks that exploit this kind of access
edit_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 edit_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.
edit_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 edit_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 edit_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.
edit_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 →