check_login_status

检查小红书登录状态

SERVERXiaoHongShu MCP SOURCE1uokun/xiaohongshu-mcp-js

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade B, identity unverified Pull the record →

This record as markdown: /tools/1uokun-xiaohongshu-mcp-js/check-login-status.md

WHAT IT DOES

What check_login_status does on XiaoHongShu MCP

AI agents call check_login_status to retrieve information from XiaoHongShu MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why check_login_status is rated Low

This tool retrieves the current login status of a user account without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns state information. The low severity reflects minimal blast radius—an agent checking login status cannot cause harm even with misuse.

From the tool's definition Tool name 'check_login_status' and description '检查小红书登录状态' (check XiaoHongShu login status) indicates querying authentication state with no side effects or data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check_login_status safely

PolicyLayer is an MCP gateway: it sits between your AI agents and XiaoHongShu MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For check_login_status, this is the rule to start with:

check_login_status Allowed

check_login_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check_login_status": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect XiaoHongShu MCP, apply this rule, and every check_login_status call is checked against it from then on.

FAQ

Questions about check_login_status

What does the check_login_status tool do? +

检查小红书登录状态. It is categorised as a Read tool in the XiaoHongShu MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_login_status? +

Register the XiaoHongShu 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 XiaoHongShu MCP. Nothing to install.

What risk level is check_login_status? +

check_login_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit check_login_status? +

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.

How do I block check_login_status completely? +

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.

What MCP server provides check_login_status? +

check_login_status is provided by the XiaoHongShu MCP server (1uokun/xiaohongshu-mcp-js). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on XiaoHongShu, and thousands of servers like it.

This server

All 3 XiaoHongShu tools →

Across the catalogue

editor_status on 010 Editor → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →