Get an existing label or create it if it doesn
AI agents use get_or_create_gmail_label to create or update resources in VaultAssist — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your VaultAssist environment.
The tool reads first (get existing label) but may write (create a new label) if one doesn't exist. Since creation is a possible outcome, Write is the most appropriate category. Creating a Gmail label is low severity — it's reversible and has minimal blast radius.
From the tool's definition 'get an existing label or create it if it doesn' (truncated) — implies creation of a new Gmail label if not found
Documented attack patterns abuse exactly the kind of access get_or_create_gmail_label gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and VaultAssist, and nothing reaches the server without passing your rules. This is the rule we recommend for get_or_create_gmail_label:
{
"version": "1",
"default": "deny",
"tools": {
"get_or_create_gmail_label": {
"limits": [
{
"counter": "get_or_create_gmail_label_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}get_or_create_gmail_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.
Get an existing label or create it if it doesn. It is categorised as a Write tool in the VaultAssist MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the VaultAssist MCP server in PolicyLayer and add a rule for get_or_create_gmail_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 VaultAssist. Nothing to install.
get_or_create_gmail_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 get_or_create_gmail_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 get_or_create_gmail_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.
get_or_create_gmail_label is provided by the VaultAssist MCP server (3xcaffeine/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from VaultAssist, 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.
79 VaultAssist tools catalogued and risk-classified — across an index of 43,000+ MCP servers.