Delete a note (moves to trash)
AI agents call delete_note to permanently remove resources in Sidvy MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool removes data irreversibly from a user's active notes. While the description notes it 'moves to trash' (suggesting potential recovery), the primary action is destructive deletion. An AI agent misusing this tool could delete important notes, causing data loss. This falls squarely under the Destructive category as it irreversibly removes user data, even if technically recoverable via a trash bin.
From the tool's definition Tool name is 'delete_note' and description states 'Delete a note (moves to trash)'. The verb 'delete' combined with the action of removing a note from active use (even if moved to trash rather than permanently purged) represents an irreversible removal of…
Attacks that exploit this kind of access
Delete a note (moves to trash). It is categorised as a Destructive tool in the Sidvy MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Sidvy MCP Server MCP server in PolicyLayer and add a rule for delete_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 Sidvy MCP Server. Nothing to install.
delete_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_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_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_note is provided by the Sidvy MCP Server MCP server (martinhjartmyr/sidvy-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 →