Restore a message from Trash back to the mailbox.
AI agents use gmail_untrash to create or update resources in Personal Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Gmail environment.
This tool creates or modifies data state reversibly by restoring trashed emails. It does not permanently delete data (which would be Destructive), merely relocates messages within Gmail's storage. The severity is medium because an agent could restore sensitive or unwanted messages, potentially exposing private content or cluttering the inbox, but the action is fully reversible via re-trashing.
From the tool's definition Tool name 'gmail_untrash' and description 'Restore a message from Trash back to the mailbox' indicate the tool modifies email state by moving messages from Trash to the mailbox—a reversible operation.
Attacks that exploit this kind of access
Restore a message from Trash back to the mailbox. It is categorised as a Write tool in the Personal Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Gmail MCP server in PolicyLayer and add a rule for gmail_untrash: 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 Personal Gmail. Nothing to install.
gmail_untrash is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the gmail_untrash 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.
Set action: deny in the PolicyLayer policy for gmail_untrash. 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.
gmail_untrash is provided by the Personal Gmail MCP server (jaingxyz/personal-gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →