Mark Gmail messages as read.
AI agents use mark_gmail_read to create or update resources in Gmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.
This tool modifies the read/unread status of emails, which is a reversible state change. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve data (Read). Marking messages as read could be misused to hide communications from the user or to manipulate email organization, posing a medium-severity risk to email integrity and visibility.
From the tool's definition Tool name 'mark_gmail_read' and description 'Mark Gmail messages as read' indicate modification of message state. Sibling tools like 'mark_gmail_important' and 'mark_gmail_unread' confirm this server modifies message metadata.
Attacks that exploit this kind of access
Mark Gmail messages as read. It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for mark_gmail_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 Gmail MCP Server. Nothing to install.
mark_gmail_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 mark_gmail_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 mark_gmail_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.
mark_gmail_read is provided by the Gmail MCP Server MCP server (stevesimpson418/gmail-mcp-server). 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 →