gmail_mark_as_read_by_query · Gmail MCP Server MCP

WHAT IT DOES

What gmail_mark_as_read_by_query does on Gmail MCP Server

AI agents use gmail_mark_as_read_by_query 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 gmail_mark_as_read_by_query needs a policy

This tool modifies email state (read/unread flag) based on query results. While the change is reversible (emails can be marked unread again), it is a write operation that alters data. It does not delete or destroy data (excluding Destructive), does not execute arbitrary code (excluding Execute), and does not involve financial transactions.

From the tool's definition Tool description states 'Mark emails matching a search query as read', which modifies email metadata (read status) reversibly. The word 'mark' indicates state modification, and 'as read' specifies the write operation being performed.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gmail_mark_as_read_by_query Rate-limited

gmail_mark_as_read_by_query 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": {
    "gmail_mark_as_read_by_query": {
      "limits": [
        {
          "counter": "gmail_mark_as_read_by_query_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 gmail_mark_as_read_by_query

What does the gmail_mark_as_read_by_query tool do? +

Mark emails matching a search query as read. Use Gmail query syntax. Requires confirmation. 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 gmail_mark_as_read_by_query? +

Register the Gmail MCP Server MCP server in PolicyLayer and add a rule for gmail_mark_as_read_by_query: 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 gmail_mark_as_read_by_query? +

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

Can I rate-limit gmail_mark_as_read_by_query? +

Yes. Add a rate_limit block to the gmail_mark_as_read_by_query 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 gmail_mark_as_read_by_query completely? +

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

gmail_mark_as_read_by_query is provided by the Gmail MCP Server MCP server (murphy360/mcp_gmail). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.