trash-email
AI agents call trash-email to permanently remove resources in MCP-server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
'Trash' operations move items to a deleted/trash folder, which is typically irreversible or requires additional steps to recover. In the context of an email automation tool for Outlook, this likely deletes or trashes an email. Since the description is empty, confidence is slightly reduced, but the name strongly implies a destructive action.
From the tool's definition Tool name 'trash-email' implies moving email to trash, which is a destructive/irreversible operation. Description is empty, so classification is based on name alone.
Attacks that exploit this kind of access
trash-email. It is categorised as a Destructive tool in the MCP-server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP-server MCP server in PolicyLayer and add a rule for trash-email: 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 MCP-server. Nothing to install.
trash-email 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-email 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-email. 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-email is provided by the MCP-server MCP server (prathapmahi/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
trash-email is one line of MCP-server's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →