gmail_users_threads_trash

Move an email thread to the trash

SERVERGoogle Workspace Gmail (gws CLI) SOURCE@gws mcp -s gmail

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/google-workspace-gmail/gmail-users-threads-trash.md

WHAT IT DOES

What gmail_users_threads_trash does on Google Workspace Gmail (gws CLI)

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

RISK

Why gmail_users_threads_trash is rated Medium

Moving an email thread to trash is a reversible write operation—the thread is not permanently deleted but moved to a recoverable location. This falls under Write rather than Destructive because trash/bin typically allows recovery. However, the blast radius is medium because an AI agent could inadvertently trash important conversations, causing user disruption.

From the tool's definition Tool name 'gmail_users_threads_trash' and description 'Move an email thread to the trash' indicate the tool modifies email state by moving threads to trash.

Risk signalsTrashes entire email threads

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs gmail_users_threads_trash safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Google Workspace Gmail (gws CLI), and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gmail_users_threads_trash, this is the rule to start with:

gmail_users_threads_trash Rate-limited

gmail_users_threads_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_users_threads_trash": {
      "limits": [
        {
          "counter": "gmail_users_threads_trash_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Google Workspace Gmail (gws CLI), apply this rule, and every gmail_users_threads_trash call is checked against it from then on.

FAQ

Questions about gmail_users_threads_trash

What does the gmail_users_threads_trash tool do? +

Move an email thread to the trash. It is categorised as a Write tool in the Google Workspace Gmail (gws CLI) 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_users_threads_trash? +

Register the Google Workspace Gmail (gws CLI) MCP server in PolicyLayer and add a rule for gmail_users_threads_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 Gmail (gws CLI). Nothing to install.

What risk level is gmail_users_threads_trash? +

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

Can I rate-limit gmail_users_threads_trash? +

Yes. Add a rate_limit block to the gmail_users_threads_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_users_threads_trash completely? +

Set action: deny in the PolicyLayer policy for gmail_users_threads_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_users_threads_trash? +

gmail_users_threads_trash is provided by the Google Workspace Gmail (gws CLI) MCP server (@gws mcp -s gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Google Workspace Gmail (gws CLI), and thousands of servers like it.

This server

All 79 Google Workspace Gmail (gws CLI) tools →

Across the catalogue

connect-gmail on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →