drive_share_list
All share-links for a file (active + revoked). Raw tokens are NEVER included — use create
This record as markdown: /tools/trekmail-mcp-server/drive-share-list.md
What drive_share_list does on TrekMail MCP Server
AI agents call drive_share_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.
Why drive_share_list is rated Low
This tool queries and retrieves data about share links without creating, modifying, deleting, or executing operations. The explicit note that 'Raw tokens are NEVER included' further confirms this is a safe read operation designed to list metadata only. The blast radius of misuse is minimal—an attacker could enumerate existing share links but cannot create new ones or access sensitive token data.
From the tool's definition Tool name 'drive_share_list' and description stating it lists 'All share-links for a file (active + revoked)' indicates a read-only operation that retrieves and enumerates existing share links without modification.
Attacks that exploit this kind of access
The rule that runs drive_share_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_share_list, this is the rule to start with:
drive_share_list is read-only, so it stays allowed. 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_share_list call is checked against it from then on.
Questions about drive_share_list
All share-links for a file (active + revoked). Raw tokens are NEVER included — use create. It is categorised as a Read tool in the TrekMail MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for drive_share_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.
drive_share_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the drive_share_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.
Set action: deny in the PolicyLayer policy for drive_share_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.
drive_share_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.
More on TrekMail MCP Server, and thousands of servers like it.
This server
Across the catalogue