imap_update_sorting_rule · Email MCP Server MCP

WHAT IT DOES

What imap_update_sorting_rule does on Email MCP Server

AI agents use imap_update_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.

WHY IT NEEDS A POLICY

Why imap_update_sorting_rule needs a policy

Email sorting rules are configuration data that affect email organization but do not delete messages or execute arbitrary operations. Updates to sorting rules are reversible and represent Write-category activity. Medium severity reflects the potential to disrupt email workflow or hide/prioritize sensitive messages if misconfigured by a compromised agent.

From the tool's definition Tool name 'imap_update_sorting_rule' indicates modification of email sorting configuration. The verb 'update' confirms data modification. Description is empty, limiting direct evidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

imap_update_sorting_rule Rate-limited

imap_update_sorting_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "imap_update_sorting_rule": {
      "limits": [
        {
          "counter": "imap_update_sorting_rule_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Email MCP Server, so you can run agents against it safely.

FAQ

Questions about imap_update_sorting_rule

What does the imap_update_sorting_rule tool do? +

imap_update_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.

How do I enforce a policy on imap_update_sorting_rule? +

Register the Email MCP Server MCP server in PolicyLayer and add a rule for imap_update_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.

What risk level is imap_update_sorting_rule? +

imap_update_sorting_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit imap_update_sorting_rule? +

Yes. Add a rate_limit block to the imap_update_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.

How do I block imap_update_sorting_rule completely? +

Set action: deny in the PolicyLayer policy for imap_update_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.

What MCP server provides imap_update_sorting_rule? +

imap_update_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.