Check if WebDAV login is successful.
AI agents call check_webdav_login to retrieve information from Nextcloud Notes without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs an authentication check, which is a read-only operation that queries the status of WebDAV connectivity. It does not create, modify, delete, execute code, or commit financial transactions. The blast radius of misuse is minimal—at worst, an agent might perform repeated login attempts, but this does not expose data or cause harm beyond potential rate-limiting.
From the tool's definition The tool name is 'check_webdav_login' and description states it 'Check if WebDAV login is successful.' This is a validation/verification operation that tests credentials without modifying any state or triggering side effects.
Attacks that exploit this kind of access
Check if WebDAV login is successful. It is categorised as a Read tool in the Nextcloud Notes MCP Server, which means it retrieves data without modifying state.
Register the Nextcloud Notes MCP server in PolicyLayer and add a rule for check_webdav_login: 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 Nextcloud Notes. Nothing to install.
check_webdav_login 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 check_webdav_login 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 check_webdav_login. 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.
check_webdav_login is provided by the Nextcloud Notes MCP server (rncz/nextcloud-notes-mcp-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 →