Add a label to a message.
AI agents use add_label_to_message to create or update resources in Mcp Gmail — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gmail environment.
This is a Write operation because it creates or modifies data reversibly. Adding a label to a message changes the message's metadata and organizational state but does not delete data or trigger external actions. The operation can be undone by removing the label.
From the tool's definition The tool 'add_label_to_message' modifies message metadata by adding a label. The server description states it enables 'read, compose, and send emails', and this sibling tool performs a reversible modification operation on existing messages.
Documented attack patterns abuse exactly the kind of access add_label_to_message gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Gmail, and nothing reaches the server without passing your rules. This is the rule we recommend for add_label_to_message:
{
"version": "1",
"default": "deny",
"tools": {
"add_label_to_message": {
"limits": [
{
"counter": "add_label_to_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} add_label_to_message 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.
Add a label to a message. It is categorised as a Write tool in the Mcp Gmail MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gmail MCP server in PolicyLayer and add a rule for add_label_to_message: 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 Gmail. Nothing to install.
add_label_to_message 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 add_label_to_message 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 add_label_to_message. 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.
add_label_to_message is provided by the Mcp Gmail MCP server (jeremyjordan/mcp-gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp 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.
9 Mcp Gmail tools catalogued and risk-classified — across an index of 43,000+ MCP servers.