删除 cookies 文件，重置登录状态。删除后需要重新登录。
AI agents call delete_cookies to permanently remove resources in Xhs Kit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes the cookies file and resets the login state. While the data loss is limited to session credentials (not user content), the action is non-reversible — once deleted, the login session is gone and re-authentication is required. This fits the Destructive category as it permanently removes stored data.
From the tool's definition 删除 cookies 文件，重置登录状态。删除后需要重新登录。 (Delete cookies file, reset login state. Re-login required after deletion.)
Attacks that exploit this kind of access
删除 cookies 文件，重置登录状态。删除后需要重新登录。. It is categorised as a Destructive tool in the Xhs Kit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Xhs Kit MCP server in PolicyLayer and add a rule for delete_cookies: 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.
delete_cookies is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_cookies 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 delete_cookies. 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.
delete_cookies 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 →