AI agents use create_label to create or update resources in Gmail MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP environment.
Creating a label is a reversible write operation that organizes emails but does not read sensitive data, execute code, delete content, or commit financial obligations. The blast radius is minimal since labels are organizational metadata. While the broader Gmail server has destructive tools (batch_delete_messages) and financial implications if compromised, this specific tool is limited to label creation.
From the tool's definition Tool name 'create_label' and description 'Create a new label' indicate a create operation that adds new metadata to Gmail without modifying or deleting existing data.
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 MCP, 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 a new label. It is categorised as a Write tool in the Gmail MCP 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 MCP. 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 (shinzo-labs/gmail-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 65 Gmail MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
65 Gmail MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.