Mark one or more Gmail messages as spam
AI agents use spam_gmail to create or update resources in Google Connections — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Google Connections environment.
This tool modifies Gmail message attributes (spam status/label) rather than permanently deleting data. While it could be misused to hide legitimate emails or disrupt user workflows, the action is reversible—users can recover messages from spam folders. This makes it Write (data modification) rather than Destructive.
From the tool's definition Tool name 'spam_gmail' and description 'Mark one or more Gmail messages as spam' indicate modification of message metadata/labels. Spam marking is a reversible classification action that changes message state without deletion.
Attacks that exploit this kind of access
Mark one or more Gmail messages as spam. It is categorised as a Write tool in the Google Connections MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Google Connections MCP server in PolicyLayer and add a rule for spam_gmail: 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 Google Connections. Nothing to install.
spam_gmail 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 spam_gmail 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 spam_gmail. 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.
spam_gmail is provided by the Google Connections MCP server (michaelzrork/google-connections-mcp). 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 →