Set or remove flags on messages. Common flags: \\Seen (read), \\Flagged (starred).
AI agents use email_set_flags to create or update resources in Apple Shortcuts — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Apple Shortcuts environment.
Setting or removing email flags is a reversible modification operation that changes message state (read/unread, starred/unstarred). While it affects email metadata, it does not delete or destroy data, nor does it execute arbitrary code or move money. It therefore falls under Write category.
From the tool's definition Tool description states 'Set or remove flags on messages' with examples like '\Seen (read)' and '\Flagged (starred)'. This modifies message metadata flags without deleting content.
Documented attack patterns abuse exactly the kind of access email_set_flags gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Apple Shortcuts, and nothing reaches the server without passing your rules. This is the rule we recommend for email_set_flags:
{
"version": "1",
"default": "deny",
"tools": {
"email_set_flags": {
"limits": [
{
"counter": "email_set_flags_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} email_set_flags 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.
Set or remove flags on messages. Common flags: \\Seen (read), \\Flagged (starred). It is categorised as a Write tool in the Apple Shortcuts MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apple Shortcuts MCP server in PolicyLayer and add a rule for email_set_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 Apple Shortcuts. Nothing to install.
email_set_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 email_set_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 email_set_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.
email_set_flags is provided by the Apple Shortcuts MCP server (@mindstone/mcp-server-apple-shortcuts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Apple Shortcuts, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
423 Apple Shortcuts tools catalogued and risk-classified — across an index of 43,000+ MCP servers.