seafile_move
A write tool on the Seafile MCP server.
This record as markdown: /tools/5p00kyy-seafile-mcp/seafile-move.md
What seafile_move does on Seafile MCP Server
AI agents use seafile_move 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.
Why seafile_move is rated Medium
Moving files or directories is a write operation that modifies metadata and structure but is reversible—the data is not deleted or lost, merely relocated. It does not execute arbitrary code, trigger financial transactions, or permanently destroy data, so it does not warrant higher-severity categories.
From the tool's definition Tool name 'seafile_move' indicates file/directory movement operations. Server description explicitly states it 'supports operations such as reading, writing, moving, and searching across libraries.' The sibling tools include destructive (seafile_delete) and…
Attacks that exploit this kind of access
The rule that runs seafile_move safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Seafile MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For seafile_move, this is the rule to start with:
seafile_move stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Seafile MCP Server, apply this rule, and every seafile_move call is checked against it from then on.
Questions about seafile_move
seafile_move is a write tool on the Seafile MCP Server MCP server. 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 seafile_move: 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.
seafile_move 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 seafile_move 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 seafile_move. 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.
seafile_move is provided by the Seafile MCP Server MCP server (5p00kyy/seafile-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Seafile MCP Server, and thousands of servers like it.
This server
Across the catalogue