删除便签
AI agents call delete_sticky_note to permanently remove resources in xigua-MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes sticky notes without the ability to undo the action. While the blast radius is limited to local note data (not system-critical or financial), the irreversible nature of deletion places it in the Destructive category rather than Write. Severity is medium because misuse would result in loss of user data but not compromise system integrity or access to sensitive information.
From the tool's definition Tool name 'delete_sticky_note' and description '删除便签' (Chinese: 'delete sticky note') explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
删除便签. It is categorised as a Destructive tool in the xigua-MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the xigua- MCP server in PolicyLayer and add a rule for delete_sticky_note: 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 xigua-MCP. Nothing to install.
delete_sticky_note 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_sticky_note 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_sticky_note. 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_sticky_note is provided by the xigua- MCP server (xiguaxiaome/xigua-mcp). 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 →