Get the sorting plan for an account.
AI agents call imap_get_sorting_plan to retrieve information from Email MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves configuration or metadata (sorting plan) for an email account. It is a read-only query operation that does not modify, create, delete, or execute actions. The blast radius is minimal as it only surfaces organizational preferences already stored in the account. No financial, destructive, or code execution impact is possible.
From the tool's definition Tool is named 'imap_get_sorting_plan' and described as 'Get the sorting plan for an account' — the verb 'Get' indicates retrieval of existing data with no modification, creation, or deletion.
Attacks that exploit this kind of access
Get the sorting plan for an account. It is categorised as a Read tool in the Email MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_get_sorting_plan: 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_get_sorting_plan is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the imap_get_sorting_plan 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_get_sorting_plan. 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_get_sorting_plan 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 →