drive_bulk_restore
Restore N trashed items in one call.
This record as markdown: /tools/trekmail-mcp-server/drive-bulk-restore.md
What drive_bulk_restore does on TrekMail MCP Server
AI agents use drive_bulk_restore to create or update resources in TrekMail MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TrekMail MCP Server environment.
Why drive_bulk_restore is rated Medium
Restoring trashed items is a reversible write operation that modifies data state (moving items from trash back to active). It is not destructive (items are recoverable from trash), not financial, and not execute (no code execution). The bulk nature and email infrastructure context suggest moderate blast radius if misused to restore unwanted volumes of data.
From the tool's definition Tool name 'drive_bulk_restore' and description 'Restore N trashed items in one call' indicate bulk restoration of deleted/trashed items to their original state.
Attacks that exploit this kind of access
The rule that runs drive_bulk_restore safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TrekMail MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For drive_bulk_restore, this is the rule to start with:
drive_bulk_restore 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.
The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every drive_bulk_restore call is checked against it from then on.
Questions about drive_bulk_restore
Restore N trashed items in one call. It is categorised as a Write tool in the TrekMail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_bulk_restore: 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 TrekMail MCP Server. Nothing to install.
drive_bulk_restore 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 drive_bulk_restore 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 drive_bulk_restore. 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.
drive_bulk_restore is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue