AI agents use flag_email to create or update resources in IMAP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IMAP MCP Server environment.
Flagging/unflagging is a metadata modification operation that is non-destructive and reversible. It does not read sensitive content, execute code, destroy data, or commit financial transactions. It falls squarely into the Write category as a state-changing operation on email objects. Severity is low because the blast radius of accidental misuse is minimal — a user can easily unflag emails if flagged incorrectly.
From the tool's definition Tool description states 'Flag or unflag email' — this modifies email metadata (flag status) reversibly without deleting or executing external code.
Documented attack patterns abuse exactly the kind of access flag_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IMAP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for flag_email:
{
"version": "1",
"default": "deny",
"tools": {
"flag_email": {
"limits": [
{
"counter": "flag_email_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}flag_email 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.
Free to start. No card required.
Flag or unflag email. It is categorised as a Write tool in the IMAP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IMAP MCP Server MCP server in PolicyLayer and add a rule for flag_email: 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 IMAP MCP Server. Nothing to install.
flag_email 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 flag_email 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 flag_email. 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.
flag_email is provided by the IMAP MCP Server MCP server (non-dirty/imap-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 IMAP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 IMAP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.