update_mail_rule
Update an existing mail filter. Pro and Agency plans only.
This record as markdown: /tools/trekmail-mcp-server/update-mail-rule.md
What update_mail_rule does on TrekMail MCP Server
AI agents use update_mail_rule 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 update_mail_rule is rated Medium
This tool modifies existing mail filter rules, which is a Write operation (reversible change to data). It does not delete rules (Destructive), execute arbitrary code (Execute), or move money (Financial). Severity is medium because misconfiguration of mail filters could cause emails to be misrouted or blocked, affecting email delivery and user productivity, but the change can be undone by updating the rule again.
From the tool's definition Tool description states "Update an existing mail filter" - the word "Update" indicates reversible modification of data (mail filter configuration).
Attacks that exploit this kind of access
The rule that runs update_mail_rule 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 update_mail_rule, this is the rule to start with:
update_mail_rule 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 update_mail_rule call is checked against it from then on.
Questions about update_mail_rule
Update an existing mail filter. Pro and Agency plans only. 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 update_mail_rule: 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.
update_mail_rule 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 update_mail_rule 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 update_mail_rule. 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.
update_mail_rule 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