nc_auth_check_status
AI agents call nc_auth_check_status to retrieve information from Nextcloud MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to verify authentication or provisioning status without modifying data. Status checks are read operations with no side effects. Low severity due to retrieving only internal state information. Confidence reduced to 0.7 because the description is empty and we rely on naming conventions and context from sibling tools.
From the tool's definition Tool name 'nc_auth_check_status' with 'check' prefix suggests a status query operation. Description is empty, limiting certainty. Sibling tools like 'check_logged_in' and 'check_provisioning_status' support classification as a read-only status check.
Attacks that exploit this kind of access
nc_auth_check_status. It is categorised as a Read tool in the Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Nextcloud MCP Server MCP server in PolicyLayer and add a rule for nc_auth_check_status: 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 MCP Server. Nothing to install.
nc_auth_check_status 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 nc_auth_check_status 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 nc_auth_check_status. 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.
nc_auth_check_status is provided by the Nextcloud MCP Server MCP server (no-smoke/nextcloud-mcp-comprehensive). 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 →