AI agents use gmail_mark_as_read to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
Marking emails as read is a reversible write operation that modifies metadata/state of Gmail messages. It does not delete data (so not Destructive), does not execute arbitrary code (so not Execute), and does not involve financial transactions. The lack of description lowers confidence slightly, but the tool name clearly indicates a write operation.
From the tool's definition Tool name 'gmail_mark_as_read' indicates it modifies email state by marking messages as read, which is a data state change. No description provided.
Attacks that exploit this kind of access
gmail_mark_as_read. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for gmail_mark_as_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 Mcp Gmail. Nothing to install.
gmail_mark_as_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_as_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_as_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_as_read is provided by the Mcp Gmail MCP server (@monsoft/mcp-gmail). 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 →