Move note to trash or delete permanently.
AI agents call delete_note to permanently remove resources in Streamline MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool performs permanent deletion of notes, which cannot be undone. Even though it offers a 'move to trash' option (reversible), the ability to 'delete permanently' qualifies it as Destructive per the rules. The high severity reflects the blast radius of an AI agent permanently deleting user notes without explicit confirmation. Confidence is high because the description unambiguously describes permanent deletion.
From the tool's definition Tool description explicitly states 'delete permanently' — an irreversible operation that removes data without recovery option.
Attacks that exploit this kind of access
Move note to trash or delete permanently. It is categorised as a Destructive tool in the Streamline MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Streamline 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 Streamline MCP. 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 Streamline MCP server (rostehea/streamline-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 →