Pause (disable) a mailbox. The mailbox will stop receiving and sending email until resumed.
AI agents use pause_mailbox 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.
Pausing a mailbox disables its ability to send and receive email, which is a significant but reversible modification (it can be resumed). This fits the Write category as it modifies the state of the mailbox without permanently deleting data. Severity is high because misuse could disrupt communications for the affected mailbox owner, potentially causing missed emails and business disruption.
From the tool's definition Pause (disable) a mailbox. The mailbox will stop receiving and sending email until resumed.
Attacks that exploit this kind of access
Pause (disable) a mailbox. The mailbox will stop receiving and sending email until resumed. 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 pause_mailbox: 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.
pause_mailbox 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 pause_mailbox 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 pause_mailbox. 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.
pause_mailbox 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 →