不带验证码的方式登录小红书账号
AI agents invoke login_without_verification_code to trigger actions in Xhs. 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 an authentication session on an external platform (Xiaohongshu) without requiring a verification code. It is an external operation with side effects (establishing a logged-in session), placing it in the Execute category. Misuse could result in unauthorized account access or session hijacking, making severity high.
From the tool's definition 登录小红书账号 (login to Xiaohongshu account); 'login_without_verification_code' — triggers an external authentication operation against a third-party platform
Documented attack patterns abuse exactly the kind of access login_without_verification_code gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xhs, and nothing reaches the server without passing your rules. This is the rule we recommend for login_without_verification_code:
{
"version": "1",
"default": "deny",
"tools": {
"login_without_verification_code": {
"limits": [
{
"counter": "login_without_verification_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}login_without_verification_code stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
不带验证码的方式登录小红书账号. It is categorised as a Execute tool in the Xhs MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Xhs MCP server in PolicyLayer and add a rule for login_without_verification_code: 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. Nothing to install.
login_without_verification_code 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 login_without_verification_code 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 login_without_verification_code. 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.
login_without_verification_code is provided by the Xhs MCP server (softegli/xhs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xhs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
3 Xhs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.