gmail_trash_message

Move a message to the trash

SERVERSage MCP SOURCEsagemcp/sagemcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/gmail-trash-message.md

WHAT IT DOES

What gmail_trash_message does on Sage MCP

AI agents call gmail_trash_message to permanently remove resources in Sage MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why gmail_trash_message is rated Critical

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'

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gmail_trash_message safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_trash_message, this is the rule to start with:

gmail_trash_message Hidden

gmail_trash_message is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

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

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every gmail_trash_message call is checked against it from then on.

FAQ

Questions about gmail_trash_message

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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →move-to-trash on Meme MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →