email_mark_read

Mark an email message as read or unread

SERVERScopeGate SOURCEhttps://mcp.scopegate.cloud/{api_key}

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-alifanov-scopegate/email-mark-read.md

WHAT IT DOES

What email_mark_read does on ScopeGate

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

RISK

Why email_mark_read is rated Medium

This tool changes the read/unread status of an email, which is a reversible write operation on message metadata. It does not retrieve data (Read), execute code (Execute), permanently delete content (Destructive), or involve financial transactions (Financial). The impact is limited to toggling a boolean flag on individual messages, making severity low even if misused by an agent.

From the tool's definition Tool name 'email_mark_read' and description 'Mark an email message as read or unread' indicate modification of email metadata state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs email_mark_read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and ScopeGate, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For email_mark_read, this is the rule to start with:

email_mark_read Rate-limited

email_mark_read 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": {
    "email_mark_read": {
      "limits": [
        {
          "counter": "email_mark_read_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect ScopeGate, apply this rule, and every email_mark_read call is checked against it from then on.

FAQ

Questions about email_mark_read

What does the email_mark_read tool do? +

Mark an email message as read or unread. It is categorised as a Write tool in the ScopeGate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on email_mark_read? +

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

What risk level is email_mark_read? +

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

Can I rate-limit email_mark_read? +

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

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

email_mark_read is provided by the ScopeGate MCP server (https://mcp.scopegate.cloud/{api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on ScopeGate, and thousands of servers like it.

This server

All 385 ScopeGate tools →

Across the catalogue

sms_mark_read on Twilio SMS MCP Server →mark-as-read on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →