mark_spam · Gmail MCP Server MCP: Risk & Policy

WHAT IT DOES

What mark_spam does on Gmail MCP Server

AI agents use mark_spam to create or update resources in Gmail MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gmail MCP Server environment.

WHY IT NEEDS A POLICY

Why mark_spam needs a policy

This tool modifies email state and folder assignment by moving messages to the Spam folder. While the action changes data organization, it is reversible (emails can be recovered from Spam and moved back to their original labels/folders). This makes it Write rather than Destructive.

From the tool's definition Tool description states it 'Mark one or more emails as spam (moves to Spam folder)' - this is a reversible modification of email state and folder location, not permanent deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_spam Rate-limited

mark_spam 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_spam": {
      "limits": [
        {
          "counter": "mark_spam_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Gmail MCP Server, so you can run agents against it safely.

FAQ

Questions about mark_spam

What does the mark_spam tool do? +

Mark one or more emails as spam (moves to Spam folder). It is categorised as a Write tool in the Gmail MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on mark_spam? +

Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for mark_spam: 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 Server. Nothing to install.

What risk level is mark_spam? +

mark_spam is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mark_spam? +

Yes. Add a rate_limit block to the mark_spam 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.

How do I block mark_spam completely? +

Set action: deny in the PolicyLayer policy for mark_spam. 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.

What MCP server provides mark_spam? +

mark_spam is provided by the Gmail MCP Server MCP server (neutral-stage/gmail-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

mark_spam is one line of Gmail MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →