Update an existing file on a remote WebDAV server with new content
AI agents use webdav_update_remote_file 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.
This tool modifies existing files on a remote server, which is a Write operation—reversible data modification. Severity is high because misconfigured AI agents could overwrite critical files across a WebDAV-accessible filesystem, potentially affecting multiple users or systems. However, it is not Destructive (files can be recovered) and not Financial.
From the tool's definition Tool name contains 'update' and description states 'Update an existing file on a remote WebDAV server with new content', indicating modification of data.
Attacks that exploit this kind of access
Update an existing file on a remote WebDAV server with new content. 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_update_remote_file: 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_update_remote_file 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_update_remote_file 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_update_remote_file. 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_update_remote_file is provided by the WebDAV MCP Server MCP server (masx200/mcp-webdav-server). 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 →