Update an existing collection in Outline
AI agents use update_collection 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.
This tool creates or modifies data reversibly, fitting the Write category. Severity is medium because unintended modifications to wiki collections could disrupt organization and access to documents, but the change is not irreversible and can be corrected by subsequent updates. High confidence based on clear descriptive language indicating data modification without deletion.
From the tool's definition Tool name 'update_collection' and description 'Update an existing collection in Outline' indicate modification of existing data.
Attacks that exploit this kind of access
Update an existing collection in Outline. 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 update_collection: 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.
update_collection 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 update_collection 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 update_collection. 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.
update_collection is provided by the Outline MCP Server MCP server (lekt9/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 →