AI agents use create_label to create or update resources in Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail environment.
Creating a label is a reversible write operation that modifies the user's email organization structure but does not delete data or execute arbitrary code. The impact is limited to adding metadata; it can be undone by deleting the label. While the description is empty, the name and context strongly indicate a write action.
From the tool's definition Tool name is 'create_label' and the server description states the server enables 'email management tasks such as reading, labeling, and searching emails.' The tool is part of a labeling suite (add_labels, delete_label, get_label_by_id, get_labels also…
Documented attack patterns abuse exactly the kind of access create_label gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Gmail, and nothing reaches the server without passing your rules. This is the rule we recommend for create_label:
{
"version": "1",
"default": "deny",
"tools": {
"create_label": {
"limits": [
{
"counter": "create_label_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_label 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.
Free to start. No card required.
create_label. It is categorised as a Write tool in the Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gmail MCP server in PolicyLayer and add a rule for create_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. Nothing to install.
create_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_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_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_label is provided by the Gmail MCP server (ivanlhz/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Gmail, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Gmail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.