登录小红书账号
AI agents invoke xiaohongshu_login to trigger actions in Xiaohongshu MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool initiates a browser-automated login to a Xiaohongshu account. It triggers an external operation (authentication session establishment) via browser automation. Misuse could result in unauthorized account access, session hijacking, or credential exposure, making it high severity. It falls under Execute because it triggers an external browser-driven operation rather than simply reading or writing data.
From the tool's definition '登录小红书账号' (Login to Xiaohongshu account) combined with server description: 'browser automation' and 'login management'
Attacks that exploit this kind of access
登录小红书账号. It is categorised as a Execute tool in the Xiaohongshu MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xiaohongshu MCP Server MCP server in PolicyLayer and add a rule for xiaohongshu_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the xiaohongshu_login 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_login. 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_login 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 →