Make this folder visible to every mailbox in the account. If the folder lives in a mailbox-personal Drive, the entire subtree (folders + files) is migrated to account-drive in one transaction; quota counters move from mailbox to account. Restrictions: folder must be top-level (parent_id=null); su...
AI agents use drive_folder_share_with_account 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.
This is a Write operation because it creates and modifies resource sharing relationships and metadata (folder visibility, quota assignments) across the account infrastructure. While the migration is atomic and the operation is idempotent (calling it again returns the folder unchanged), it irreversibly changes who can access the data and how quotas are tracked.
From the tool's definition The tool description states it makes a folder 'visible to every mailbox in the account' and performs a migration of folders and files 'in one transaction' with 'quota counters move from mailbox to account.' This modifies data ownership and accessibility,…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Make this folder visible to every mailbox in the account. If the folder lives in a mailbox-personal Drive, the entire subtree (folders + files) is migrated to account-drive in one transaction; quota counters move from mailbox to account. Restrictions: folder must be top-level (parent_id=null); subtree must contain ≤ 1000 files; account pool must have room for the migrated bytes. Idempotent — calling on an already-shared folder returns it unchanged. 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_folder_share_with_account: 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_folder_share_with_account 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_folder_share_with_account 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_folder_share_with_account. 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_folder_share_with_account 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.
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 →