AI agents call empty-trash to permanently remove resources in SupaThings MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Emptying a trash permanently deletes all items within it, which is an irreversible destructive action. The name is idiomatic across many applications (macOS, task managers like Things 3) and consistently means permanent deletion. Combined with the context of a Things 3 management server, this almost certainly purges all trashed tasks/projects permanently. Confidence is slightly reduced due to the empty description.
From the tool's definition Tool name 'empty-trash' strongly implies irreversible deletion of trashed items; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access empty-trash gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SupaThings MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for empty-trash:
{
"version": "1",
"default": "deny",
"hide": [
"empty-trash"
]
}empty-trash disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
empty-trash. It is categorised as a Destructive tool in the SupaThings MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the SupaThings MCP server in PolicyLayer and add a rule for empty-trash: 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 SupaThings MCP. Nothing to install.
empty-trash 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 empty-trash 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 empty-trash. 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.
empty-trash is provided by the SupaThings MCP server (soycanopa/supathings-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SupaThings MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
37 SupaThings MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.