Add/remove labels on a message (e.g. mark read by removing UNREAD).
AI agents use gmail_message_modify to create or update resources in Google Workspace — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Workspace environment.
The tool modifies message metadata (labels, read/unread status) but does not delete the message itself or prevent it from being recovered. It is reversible—labels can be re-added and read status can be changed back. This qualifies as Write rather than Destructive.
From the tool's definition Tool description states it can 'Add/remove labels on a message' and gives the example of 'mark read by removing UNREAD'. This is a state modification operation on existing data (labels and read status).
Attacks that exploit this kind of access
Add/remove labels on a message (e.g. mark read by removing UNREAD). It is categorised as a Write tool in the Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Workspace MCP server in PolicyLayer and add a rule for gmail_message_modify: 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 Google Workspace. Nothing to install.
gmail_message_modify 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_message_modify 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_message_modify. 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_message_modify is provided by the Google Workspace MCP server (rajool/google-workspace-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 →