Create a new Gmail label
AI agents use create_email_label to create or update resources in Gmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.
Creating a label is a reversible write operation that adds organizational structure to Gmail. It does not read sensitive email content, execute external code, delete data, or involve financial transactions. The blast radius if misused is minimal — an agent could create many labels, but this causes no data loss or security breach. Severity is low because label creation is a low-impact organizational action.
From the tool's definition Tool name is 'create_email_label' and description states 'Create a new Gmail label' — this creates new metadata/organizational data in Gmail without modifying, deleting, or sending email content.
Attacks that exploit this kind of access
Create a new Gmail label. It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for create_email_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 MCP Server. Nothing to install.
create_email_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 create_email_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 create_email_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.
create_email_label is provided by the Gmail MCP Server MCP server (meyannis/mcpgmail). 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 →