suspend_mailbox_login
Stop someone signing in while their mail keeps arriving: webmail, IMAP, SMTP, app passwords, Drive device passwords and reset links are all refused and open sessions end, but delivery is untouched and nothing bounces. Every app password and Drive device password of the mailbox is revoked, not jus...
This record as markdown: /tools/trekmail-mcp-server/suspend-mailbox-login.md
What suspend_mailbox_login does on TrekMail MCP Server
AI agents use suspend_mailbox_login 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 suspend_mailbox_login is rated Medium
An AI agent can call suspend_mailbox_login faster than any human can review: one bad instruction and it creates or modifies resources in TrekMail MCP Server by the hundred, each call as confident as the last.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs suspend_mailbox_login 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 suspend_mailbox_login, this is the rule to start with:
suspend_mailbox_login 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 suspend_mailbox_login call is checked against it from then on.
Questions about suspend_mailbox_login
Stop someone signing in while their mail keeps arriving: webmail, IMAP, SMTP, app passwords, Drive device passwords and reset links are all refused and open sessions end, but delivery is untouched and nothing bounces. Every app password and Drive device password of the mailbox is revoked, not just paused. Use for a client who has not paid; pause_mailbox is harsher and stops delivery too. Shared mailboxes are refused — suspend their members instead. Lift with resume_mailbox_login. 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 suspend_mailbox_login: 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.
suspend_mailbox_login 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 suspend_mailbox_login 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 suspend_mailbox_login. 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.
suspend_mailbox_login 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