drive_trash_list

Soft-deleted files + folders in the space, newest-first. Cursor-paginated by deleted_at; default per_page=50.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/drive-trash-list.md

WHAT IT DOES

What drive_trash_list does on TrekMail MCP Server

AI agents call drive_trash_list to retrieve information from TrekMail MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why drive_trash_list is rated Low

This tool only queries data from a trash/recycle bin without creating, modifying, deleting, or executing operations. Listing soft-deleted items is a read-only action. The low severity reflects that unauthorized access to deleted file metadata has limited blast radius compared to actually restoring, permanently deleting, or modifying those files.

From the tool's definition Tool name 'drive_trash_list' and description indicate it retrieves and lists soft-deleted files and folders with pagination.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs drive_trash_list 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_trash_list, this is the rule to start with:

drive_trash_list Allowed

drive_trash_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "drive_trash_list": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every drive_trash_list call is checked against it from then on.

FAQ

Questions about drive_trash_list

What does the drive_trash_list tool do? +

Soft-deleted files + folders in the space, newest-first. Cursor-paginated by deleted_at; default per_page=50. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on drive_trash_list? +

Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_trash_list: 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.

What risk level is drive_trash_list? +

drive_trash_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit drive_trash_list? +

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

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

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

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →