Set or unset the $seen flag on one or more emails.
AI agents use mail_mark_email_read to create or update resources in Pyfastmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Pyfastmail environment.
This tool modifies email state (the $seen flag) but does not create, delete, or permanently alter email content. The change is reversible—emails can be marked unread and read again. While not destructive, it is a Write operation that changes data properties. Given the server's full account access and that bulk operations could affect many emails, the severity is medium rather than low.
From the tool's definition Tool name 'mail_mark_email_read' and description 'Set or unset the $seen flag on one or more emails' indicates modification of email metadata state. The $seen flag is a reversible property that can be toggled on or off.
Attacks that exploit this kind of access
Set or unset the $seen flag on one or more emails. It is categorised as a Write tool in the Pyfastmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Pyfastmail MCP server in PolicyLayer and add a rule for mail_mark_email_read: 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 Pyfastmail. Nothing to install.
mail_mark_email_read 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 mail_mark_email_read 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 mail_mark_email_read. 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.
mail_mark_email_read is provided by the Pyfastmail MCP server (pjosols/pyfastmail-mcp). 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 →