AI agents call check_login_status to retrieve information from Xhs Kit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple file existence check and returns login status without creating, modifying, deleting, or executing any operations. It is a pure read operation with minimal security impact—even if misused by an AI agent, it only reveals whether a session exists locally and does not enable unauthorized actions.
From the tool's definition Tool name 'check_login_status' and description stating it only checks if cookies file exists (只检查 cookies 文件是否存在), indicating a read-only operation that queries local authentication state without modification or side effects.
Attacks that exploit this kind of access
检查小红书登录状态（只检查 cookies 文件是否存在）. It is categorised as a Read tool in the Xhs Kit MCP Server, which means it retrieves data without modifying state.
Register the Xhs Kit MCP server in PolicyLayer and add a rule for check_login_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 Xhs Kit. Nothing to install.
check_login_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 check_login_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 check_login_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.
check_login_status is provided by the Xhs Kit MCP server (luweizheng/xhs-kit). 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 →