imap_add_sorting_rule
AI agents use imap_add_sorting_rule to create or update resources in Email MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Email MCP Server environment.
Adding an IMAP sorting rule creates or modifies email filter/organizational settings reversibly. This is a Write operation—it changes system configuration but does not execute arbitrary commands, delete data, or move money. Severity is medium because misconfigured sorting rules could misdirect emails but are easily correctable and have limited blast radius compared to destructive operations.
From the tool's definition Tool name 'imap_add_sorting_rule' indicates it creates or adds a new sorting rule in IMAP. The 'add' verb clearly indicates a write operation that modifies email organization settings. No description provided, lowering confidence slightly.
Attacks that exploit this kind of access
imap_add_sorting_rule. It is categorised as a Write tool in the Email MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_add_sorting_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 Email MCP Server. Nothing to install.
imap_add_sorting_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 imap_add_sorting_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 imap_add_sorting_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.
imap_add_sorting_rule is provided by the Email MCP Server MCP server (sventern/mcp_email). 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 →