Resume a paused (disabled) mailbox. The mailbox will start receiving and sending email again.
AI agents use resume_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.
This tool changes mailbox configuration state reversibly - a paused mailbox can be paused again if needed. It does not delete data or trigger irreversible changes, nor does it execute arbitrary code. While it affects operational status, the primary action is state modification (Write category).
From the tool's definition Tool description states 'Resume a paused (disabled) mailbox. The mailbox will start receiving and sending email again.' This modifies the state of a mailbox from paused/disabled to active, enabling email functionality.
Attacks that exploit this kind of access
Resume a paused (disabled) mailbox. The mailbox will start receiving and sending email again. 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 resume_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.
resume_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 resume_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 resume_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.
resume_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 →