update-email
Modify single email labels/status. Returns: updated message with new labelIds. Use when: marking one email read/unread/starred. For multiple: use batch-update-emails. Labels: UNREAD, STARRED, IMPORTANT, INBOX.
This record as markdown: /tools/199-biotechnologies-mcp-google/update-email.md
What update-email does on MCP Google Workspace
AI agents use update-email to create or update resources in MCP Google Workspace, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Google Workspace environment.
Why update-email is rated Medium
This tool modifies email metadata (labels and status flags) reversibly without deleting content or executing arbitrary operations. It falls under Write rather than Read (modifies data), Execute (doesn't run code/commands), or Destructive (changes are reversible).
From the tool's definition Tool description states 'Modify single email labels/status' and examples include 'marking one email read/unread/starred'. The server description confirms 'full create, read, update, and delete capabilities' with OAuth2 authentication to Gmail.
Attacks that exploit this kind of access
The rule that runs update-email safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Google Workspace, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update-email, this is the rule to start with:
update-email 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.
The button opens the PolicyLayer dashboard: create your workspace, connect MCP Google Workspace, apply this rule, and every update-email call is checked against it from then on.
Questions about update-email
Modify single email labels/status. Returns: updated message with new labelIds. Use when: marking one email read/unread/starred. For multiple: use batch-update-emails. Labels: UNREAD, STARRED, IMPORTANT, INBOX. It is categorised as a Write tool in the MCP Google Workspace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Google Workspace MCP server in PolicyLayer and add a rule for update-email: 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 Google Workspace. Nothing to install.
update-email 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 update-email 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 update-email. 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.
update-email is provided by the MCP Google Workspace MCP server (199-mcp/mcp-google). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Google Workspace, and thousands of servers like it.
This server
Across the catalogue