gmail_trash_message

THE RISK

Critical Risk

Moving a message to trash is effectively a destructive action — while Gmail trash can be recovered within 30 days, it removes the message from the inbox and is often considered irreversible in automated/agent contexts. The user's data is removed from its original location. Given the potential for an AI agent to trash important emails at scale in a multi-tenant environment, severity is high.

From the tool's definition 'gmail_trash_message' and 'Move a message to the trash'

Documented attack patterns abuse exactly the kind of access gmail_trash_message gives an agent:

HOW TO CONTROL GMAIL_TRASH_MESSAGE

PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gmail_trash_message:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "gmail_trash_message"
  ]
}

gmail_trash_message disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Sage MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Sage MCP tools

Financial copilot_add_seats Add Copilot seats for specified users in an organization Financial cursor_set_user_spend_limit Set a spending limit in USD for a specific team member Destructive claude_code_delete_invite Delete a pending invitation Destructive claude_code_remove_user Remove a user from the organization Destructive codex_delete_user Remove a user from the organization Destructive confluence_delete_page Delete a Confluence page by ID Destructive copilot_remove_seats Remove Copilot seats for specified users in an organization Destructive cursor_remove_member Remove a member from the Cursor team by user ID

All 359 Sage MCP tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Sage MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the gmail_trash_message tool do? +

Move a message to the trash. It is categorised as a Destructive tool in the Sage MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on gmail_trash_message? +

Register the Sage MCP server in PolicyLayer and add a rule for gmail_trash_message: 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 Sage MCP. Nothing to install.

What risk level is gmail_trash_message? +

gmail_trash_message is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit gmail_trash_message? +

Yes. Add a rate_limit block to the gmail_trash_message 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.

How do I block gmail_trash_message completely? +

Set action: deny in the PolicyLayer policy for gmail_trash_message. 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.

What MCP server provides gmail_trash_message? +

gmail_trash_message is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sage MCP tool call.

Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN SAGE →

Free to start. No card required.

359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT GMAIL_TRASH_MESSAGE ON SAGE MCP DOES

// THE RISK

// HOW TO CONTROL GMAIL_TRASH_MESSAGE

// EXPLORE