gmail_message_trash · Google Workspace MCP: Risk & Policy

WHAT IT DOES

What gmail_message_trash does on Google Workspace

AI agents use gmail_message_trash to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.

WHY IT NEEDS A POLICY

Why gmail_message_trash needs a policy

This tool modifies data state (moves a message) rather than permanently deleting it. Although the change is reversible for 30 days, after that period it becomes effectively destructive. The reversibility within 30 days and the common user expectation that trash is recoverable justifies classification as Write rather than Destructive.

From the tool's definition Tool description states 'Move a message to Trash (reversible for 30 days).' The action modifies message state by moving it to Trash, which is reversible within 30 days.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gmail_message_trash Rate-limited

gmail_message_trash stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "gmail_message_trash": {
      "limits": [
        {
          "counter": "gmail_message_trash_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Google Workspace, so you can run agents against it safely.

FAQ

Questions about gmail_message_trash

What does the gmail_message_trash tool do? +

Move a message to Trash (reversible for 30 days). It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on gmail_message_trash? +

Register the Google Workspace MCP server in PolicyLayer and add a rule for gmail_message_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 Google Workspace. Nothing to install.

What risk level is gmail_message_trash? +

gmail_message_trash is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gmail_message_trash? +

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

How do I block gmail_message_trash completely? +

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

What MCP server provides gmail_message_trash? +

gmail_message_trash is provided by the Google Workspace MCP server (rajool/google-workspace-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.