Move a note to trash
AI agents call trash_note to permanently remove resources in Bear MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Moving a note to trash is a destructive action that removes the note from active use. While some trash implementations allow recovery, trashing is generally considered irreversible from a workflow perspective and the user's data is effectively removed. This warrants a Destructive classification with high severity since an AI agent misusing this could cause significant data loss across notes.
From the tool's definition 'trash_note' - 'Move a note to trash'
Attacks that exploit this kind of access
Move a note to trash. It is categorised as a Destructive tool in the Bear MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bear MCP Server MCP server in PolicyLayer and add a rule for trash_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 Bear MCP Server. Nothing to install.
trash_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 trash_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 trash_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.
trash_note is provided by the Bear MCP Server MCP server (philgetzen/bear-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 →