检查小红书登录状态
AI agents call xiaohongshu_check_status to retrieve information from Xiaohongshu MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Status checking is a read-only operation that retrieves information about the current login state without modifying, deleting, or executing any actions. It has minimal blast radius if misused by an AI agent, as it only reveals authentication status without enabling unauthorized access or data modification.
From the tool's definition Tool name and description indicate status checking operation: 'xiaohongshu_check_status' and '检查小红书登录状态' (check Xiaohongshu login status). This is a query operation with no side effects.
Attacks that exploit this kind of access
检查小红书登录状态. It is categorised as a Read tool in the Xiaohongshu MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Xiaohongshu MCP Server MCP server in PolicyLayer and add a rule for xiaohongshu_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 Xiaohongshu MCP Server. Nothing to install.
xiaohongshu_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 xiaohongshu_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 xiaohongshu_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.
xiaohongshu_check_status is provided by the Xiaohongshu MCP Server MCP server (muhenan/xiaohongshu-mcp-python). 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 →