pause_mailbox

Pause (disable) a mailbox. The mailbox will stop receiving and sending email until resumed.

SERVERTrekMail MCP Server SOURCEtrekmail/mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/trekmail-mcp-server/pause-mailbox.md

WHAT IT DOES

What pause_mailbox does on TrekMail MCP Server

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.

RISK

Why pause_mailbox is rated Medium

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

RECOMMENDED RULE

The rule that runs pause_mailbox 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 pause_mailbox, this is the rule to start with:

pause_mailbox Rate-limited

pause_mailbox 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pause_mailbox": {
      "limits": [
        {
          "counter": "pause_mailbox_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TrekMail MCP Server, apply this rule, and every pause_mailbox call is checked against it from then on.

FAQ

Questions about pause_mailbox

What does the pause_mailbox tool do? +

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.

How do I enforce a policy on pause_mailbox? +

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.

What risk level is pause_mailbox? +

pause_mailbox is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit pause_mailbox? +

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.

How do I block pause_mailbox completely? +

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.

What MCP server provides pause_mailbox? +

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.

KEEP EXPLORING

More on TrekMail MCP Server, and thousands of servers like it.

This server

All 248 TrekMail MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →