Set the directory where sorting plans are stored.
AI agents use imap_set_sorting_plans_directory 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.
This tool modifies system configuration (directory settings for sorting plans) rather than reading data. While configuration changes are generally reversible and don't directly access email content, misconfiguration could impact email sorting functionality or redirect data storage to unintended locations.
From the tool's definition The tool name contains 'set' and the description states it 'Set[s] the directory where sorting plans are stored,' indicating modification of configuration data.
Attacks that exploit this kind of access
Set the directory where sorting plans are stored. 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_set_sorting_plans_directory: 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_set_sorting_plans_directory 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_set_sorting_plans_directory 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_set_sorting_plans_directory. 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_set_sorting_plans_directory 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 →