Mark a message as read by removing the UNREAD label.
AI agents use mark_message_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.
This tool modifies message metadata (read/unread status) rather than reading data or executing arbitrary operations. The change is reversible (messages can be marked unread again), and the blast radius is limited to email metadata state. It does not delete data, access sensitive content beyond what the user already has access to, or trigger external operations.
From the tool's definition Tool marks a message as read by removing the UNREAD label, which modifies the state/metadata of an existing message. The description explicitly states an action that changes data: 'removing the UNREAD label'.
Documented attack patterns abuse exactly the kind of access mark_message_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Gmail, and nothing reaches the server without passing your rules. This is the rule we recommend for mark_message_read:
{
"version": "1",
"default": "deny",
"tools": {
"mark_message_read": {
"limits": [
{
"counter": "mark_message_read_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} mark_message_read 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.
Mark a message as read by removing the UNREAD label. 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 mark_message_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.
mark_message_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_message_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_message_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_message_read is provided by the Mcp Gmail MCP server (jeremyjordan/mcp-gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Gmail, 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.
9 Mcp Gmail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.