Move or rename a file or directory on a remote WebDAV server
AI agents use webdav_move_remote_item to create or update resources in WebDAV MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WebDAV MCP Server environment.
Moving/renaming files is a Write operation: it modifies data structures and organizational state without deletion, and the action is reversible (the item can be moved back). It is not Destructive because the data itself is preserved.
From the tool's definition Tool performs 'Move or rename a file or directory on a remote WebDAV server' — modifies file system state by relocating items, which is reversible through a counter-move operation.
Documented attack patterns abuse exactly the kind of access webdav_move_remote_item gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WebDAV MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for webdav_move_remote_item:
{
"version": "1",
"default": "deny",
"tools": {
"webdav_move_remote_item": {
"limits": [
{
"counter": "webdav_move_remote_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} webdav_move_remote_item 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.
Free to start. No card required.
Move or rename a file or directory on a remote WebDAV server. It is categorised as a Write tool in the WebDAV MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WebDAV MCP Server MCP server in PolicyLayer and add a rule for webdav_move_remote_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 WebDAV MCP Server. Nothing to install.
webdav_move_remote_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 webdav_move_remote_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 webdav_move_remote_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.
webdav_move_remote_item is provided by the WebDAV MCP Server MCP server (laubplusco/mcp-webdav-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from WebDAV MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 WebDAV MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.