Copy a file or directory to a new location.
AI agents use copy_item to create or update resources in Seafile MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Seafile MCP Server environment.
Copying creates or duplicates data in a new location, which is a Write operation (reversible, no deletion). It ranks below Destructive (no irreversible loss) and below Execute (no arbitrary code execution). Severity is medium because unintended copies could consume storage or create confusion, but the effect is reversible via deletion. Confidence is high because 'copy' unambiguously means creating a duplicate.
From the tool's definition Tool description states 'Copy a file or directory to a new location' — this creates new data (a copy) at a destination, which is a reversible write operation.
Attacks that exploit this kind of access
Copy a file or directory to a new location. It is categorised as a Write tool in the Seafile MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Seafile MCP Server MCP server in PolicyLayer and add a rule for copy_item: 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 Seafile MCP Server. Nothing to install.
copy_item 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 copy_item 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 copy_item. 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.
copy_item is provided by the Seafile MCP Server MCP server (setugk/seafile-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 →