check_logged_in
AI agents call check_logged_in 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 performs a status check of the current login state, which is a read-only operation with no side effects. No data is created, modified, deleted, or financial transactions are involved. The naming convention and context among sibling authentication tools suggest this is an informational query. Low severity assigned due to minimal blast radius—a misused status check cannot modify or delete data.
From the tool's definition Tool name 'check_logged_in' indicates it queries authentication status without modifying state. Description is empty, limiting certainty.
Attacks that exploit this kind of access
check_logged_in. 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 check_logged_in: 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.
check_logged_in 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_logged_in 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_logged_in. 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_logged_in 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 →