Updates an existing Gmail label
AI agents use update_label to create or update resources in Gmail AutoAuth MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail AutoAuth MCP Server environment.
The tool modifies Gmail labels (a reversible, non-destructive change). It does not delete labels (which would be Destructive), read data (Read), execute arbitrary operations (Execute), or move money (Financial). Severity is medium because label updates could affect email organization and filtering if manipulated maliciously, but the blast radius is limited to label metadata.
From the tool's definition Tool description states 'Updates an existing Gmail label' — a direct modification of existing data in Gmail's label system without deletion or creation.
Attacks that exploit this kind of access
Updates an existing Gmail label. It is categorised as a Write tool in the Gmail AutoAuth MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail AutoAuth MCP Server MCP server in PolicyLayer and add a rule for update_label: 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 Gmail AutoAuth MCP Server. Nothing to install.
update_label 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_label 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_label. 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_label is provided by the Gmail AutoAuth MCP Server MCP server (sepehrshapouri/gmail-mcp-server). 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 →