Mark a message read (remove UNREAD) or unread (add UNREAD). Pass isRead=false to mark unread.
AI agents use gmail_mark_read to create or update resources in Personal Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Personal Gmail environment.
This tool modifies message metadata (the UNREAD flag) in Gmail, changing the read/unread state of emails. This is a reversible write operation—the state can be toggled back. It does not retrieve data (Read), execute external commands (Execute), permanently delete data (Destructive), or involve financial transactions (Financial).
From the tool's definition Tool description states it can 'Mark a message read (remove UNREAD) or unread (add UNREAD)', indicating modification of message state/metadata.
Attacks that exploit this kind of access
Mark a message read (remove UNREAD) or unread (add UNREAD). Pass isRead=false to mark unread. It is categorised as a Write tool in the Personal Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Personal Gmail MCP server in PolicyLayer and add a rule for gmail_mark_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 Personal Gmail. Nothing to install.
gmail_mark_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 gmail_mark_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 gmail_mark_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.
gmail_mark_read is provided by the Personal Gmail MCP server (jaingxyz/personal-gmail-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 →