AI agents use flag-message to create or update resources in Apple Mail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Mail environment.
Flagging a message modifies its metadata/state reversibly without deleting or executing code. This is a write operation. Severity is medium because mass flagging could clutter a user's workflow, but the action is reversible. Confidence is reduced (0.75) because the tool description is empty; classification relies on the sibling batch operations and server context for inference.
From the tool's definition Tool name 'flag-message' combined with sibling tool 'batch-flag-messages' and 'batch-unflag-messages' indicates state modification of messages. The server description states it 'manage[s] emails in Apple Mail' and uses AppleScript for local interaction.
Documented attack patterns abuse exactly the kind of access flag-message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Mail, and nothing reaches the server without passing your rules. This is the rule we recommend for flag-message:
{
"version": "1",
"default": "deny",
"tools": {
"flag-message": {
"limits": [
{
"counter": "flag-message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}flag-message 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-message. It is categorised as a Write tool in the Apple Mail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Mail MCP server in PolicyLayer and add a rule for flag-message: 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 Apple Mail. Nothing to install.
flag-message 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-message 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-message. 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-message is provided by the Apple Mail MCP server (sweetrb/apple-mail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 40 Apple Mail tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
40 Apple Mail tools catalogued and risk-classified — across an index of 42,500+ MCP servers.