set_mailboxes_drive_access
Set the Drive access level on many mailboxes at once. Choose the mailboxes with exactly ONE of: mailbox_ids (an explicit list), domain_id (every mailbox on that domain — the usual choice for a reseller applying a rule to one client), or all (every mailbox on the account). Shared mailboxes in the ...
This record as markdown: /tools/trekmail-mcp-server/set-mailboxes-drive-access.md
What set_mailboxes_drive_access does on TrekMail MCP Server
AI agents use set_mailboxes_drive_access 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 set_mailboxes_drive_access is rated Medium
Modifies access control settings across multiple mailboxes reversibly, affecting user permissions and data accessibility.
From the tool's definition Set the Drive access level on many mailboxes at once
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs set_mailboxes_drive_access 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 set_mailboxes_drive_access, this is the rule to start with:
set_mailboxes_drive_access 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 set_mailboxes_drive_access call is checked against it from then on.
Questions about set_mailboxes_drive_access
Set the Drive access level on many mailboxes at once. Choose the mailboxes with exactly ONE of: mailbox_ids (an explicit list), domain_id (every mailbox on that domain — the usual choice for a reseller applying a rule to one client), or all (every mailbox on the account). Shared mailboxes in the selection are skipped, since they have no Drive of their own. Nothing is deleted: files already stored stay until they are removed. Returns how many mailboxes matched, how many changed, and how many were skipped; mailboxes already on the requested level count as matched but not updated, so the call is safe to repeat. 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 set_mailboxes_drive_access: 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.
set_mailboxes_drive_access 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 set_mailboxes_drive_access 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 set_mailboxes_drive_access. 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.
set_mailboxes_drive_access 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