rotate_mailbox_app_password
Replace an app password with a new secret under the same name. The old secret stops working at once and the mail apps using it are signed out until the user enters the new one. Returns the new row (new data.id) with data.password once, plus replaced_id. ${ONE_TIME_SECRET_HANDLING} Use this when t...
This record as markdown: /tools/trekmail-mcp-server/rotate-mailbox-app-password.md
What rotate_mailbox_app_password does on TrekMail MCP Server
AI agents use rotate_mailbox_app_password 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 rotate_mailbox_app_password is rated Medium
Modifies mailbox credentials reversibly; high blast radius due to account access disruption and credential exposure.
From the tool's definition Replace app password with new secret, old secret stops working, mail apps signed out
Attacks that exploit this kind of access
The rule that runs rotate_mailbox_app_password 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 rotate_mailbox_app_password, this is the rule to start with:
rotate_mailbox_app_password 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 rotate_mailbox_app_password call is checked against it from then on.
Questions about rotate_mailbox_app_password
Replace an app password with a new secret under the same name. The old secret stops working at once and the mail apps using it are signed out until the user enters the new one. Returns the new row (new data.id) with data.password once, plus replaced_id. ${ONE_TIME_SECRET_HANDLING} Use this when the user lost the password or wants a fresh one; to stop a device for good, use revoke_mailbox_app_password. Fails with conflict if the app password was already revoked. 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 rotate_mailbox_app_password: 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.
rotate_mailbox_app_password 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 rotate_mailbox_app_password 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 rotate_mailbox_app_password. 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.
rotate_mailbox_app_password 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