trash-email · Gmail Plugin MCP Server MCP: Risk & Policy

WHAT IT DOES

What trash-email does on Gmail Plugin MCP Server

AI agents use trash-email to create or update resources in Gmail Plugin MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail Plugin MCP Server environment.

WHY IT NEEDS A POLICY

Why trash-email needs a policy

Trashing an email modifies the email's state (moves it to trash folder) but is reversible—users can restore from trash. This makes it Write rather than Destructive. The blast radius is medium: an AI agent trashing emails without authorization could disrupt user workflows, but recovery is possible. This is less severe than permanent deletion (which would be Destructive) or financial operations.

From the tool's definition Tool name 'trash-email' indicates moving an email to trash, which modifies email state. Server description lists 'trash' as a managed operation. No description provided for the tool itself, limiting confidence slightly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

trash-email Rate-limited

trash-email 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": {
    "trash-email": {
      "limits": [
        {
          "counter": "trash-email_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 Gmail Plugin MCP Server, so you can run agents against it safely.

FAQ

Questions about trash-email

What does the trash-email tool do? +

trash-email. It is categorised as a Write tool in the Gmail Plugin MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on trash-email? +

Register the Gmail Plugin 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 Gmail Plugin MCP Server. Nothing to install.

What risk level is trash-email? +

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

Can I rate-limit trash-email? +

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.

How do I block trash-email completely? +

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.

What MCP server provides trash-email? +

trash-email is provided by the Gmail Plugin MCP Server MCP server (sanchisingh01/mcp-server---gmail-plugin-for-claude-desktop). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.