gmail_users_threads_untrash

Restore an email thread from 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-untrash.md

What gmail_users_threads_untrash does on Google Workspace Gmail (gws CLI)

AI agents use gmail_users_threads_untrash 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.

Why gmail_users_threads_untrash is rated Medium

This tool modifies the state of email data by restoring (moving) a thread from trash, which is a reversible write operation. It does not delete data permanently (would be Destructive) or execute arbitrary code (would be Execute).

From the tool's definition Tool name 'gmail_users_threads_untrash' and description 'Restore an email thread from the trash' indicate a modification operation that moves a thread from trash back to active state.

Risk signalsRestores trashed threads

Questions about gmail_users_threads_untrash

What does the gmail_users_threads_untrash tool do? +

Restore an email thread from 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_untrash? +

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

What risk level is gmail_users_threads_untrash? +

gmail_users_threads_untrash 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_untrash? +

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

How do I block gmail_users_threads_untrash completely? +

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

What MCP server provides gmail_users_threads_untrash? +

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

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Google Workspace Gmail (gws CLI)'s. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.