Add flags to emails
AI agents use add_flags to create or update resources in MCP Mail Organizer — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Mail Organizer environment.
Adding flags to emails is a non-destructive write operation that modifies email metadata. Flags are standard email attributes (like starred, important, etc.) that can be freely added, modified, or removed. This has minimal blast radius and no irreversible consequences, making it a Write-category tool with low severity.
From the tool's definition Tool name 'add_flags' and description 'Add flags to emails' indicate modification of email metadata (flags/labels). Flags are reversible attributes that can be added or removed without deleting or executing operations.
Attacks that exploit this kind of access
Add flags to emails. It is categorised as a Write tool in the MCP Mail Organizer MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Mail Organizer MCP server in PolicyLayer and add a rule for add_flags: 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 MCP Mail Organizer. Nothing to install.
add_flags 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 add_flags 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 add_flags. 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.
add_flags is provided by the MCP Mail Organizer MCP server (neomody77/mcp-mail-organizer). 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 →