Mark a message as read in Hermes's inbox (removes the UNREAD label).
AI agents use mail_mark_read to create or update resources in Hermes Google — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Hermes Google environment.
This tool modifies message state reversibly by changing a label, which constitutes a Write operation. The impact is minimal (only removes unread status, does not delete or move data), resulting in low severity. The confidence is high because the description clearly indicates a state change operation.
From the tool's definition Tool description states it 'Mark[s] a message as read' by removing the UNREAD label, which is a modification of message metadata/state.
Attacks that exploit this kind of access
Mark a message as read in Hermes's inbox (removes the UNREAD label). It is categorised as a Write tool in the Hermes Google MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Hermes Google MCP server in PolicyLayer and add a rule for mail_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 Hermes Google. Nothing to install.
mail_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 mail_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 mail_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.
mail_mark_read is provided by the Hermes Google MCP server (jimmy-larsson/hermes-google). 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 →