Medium Risk

untrash_message

Remove a message from the trash

How to control untrash_message ↓

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

Medium Risk

This tool restores a message from trash back to the inbox/original location. It is a reversible write operation — it modifies the message's location/state without permanently deleting or creating data. It is the inverse of trashing, and the action can be undone by trashing again.

From the tool's definition Remove a message from the trash

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

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "untrash_message": {
      "limits": [
        {
          "counter": "untrash_message_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

untrash_message 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.

  1. Create a free account and register Gmail MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Go deeper

What does the untrash_message tool do? +

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

How do I enforce a policy on untrash_message? +

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

What risk level is untrash_message? +

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

Can I rate-limit untrash_message? +

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

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

untrash_message is provided by the Gmail MCP server (shinzo-labs/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gmail MCP tool call.

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

Free to start. No card required.

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

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.