Read a specific byte range from a file on a remote WebDAV server (similar to HTTP 206 Partial Content)
AI agents call webdav_range_request to retrieve information from WebDAV MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file content without side effects. It performs a bounded, read-only operation on a remote file system. The blast radius is minimal—it can only access data the authenticated user already has permission to read. No data is created, modified, deleted, or executed.
From the tool's definition Tool description explicitly states 'Read a specific byte range from a file' with no modification, deletion, or execution capability. The WebDAV operation is a standard HTTP 206 Partial Content request, which is inherently a read-only operation.
Attacks that exploit this kind of access
Read a specific byte range from a file on a remote WebDAV server (similar to HTTP 206 Partial Content). It is categorised as a Read tool in the WebDAV MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WebDAV MCP Server MCP server in PolicyLayer and add a rule for webdav_range_request: 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_range_request is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the webdav_range_request 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_range_request. 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_range_request 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 →