email_mark_read · UnClick MCP: Risk & Policy

WHAT IT DOES

What email_mark_read does on UnClick

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

PARAMETERS

Parameter	Type	Required
`uid`	string	Yes
`email`	string	—
`folder`	string	—
`password`	string	—

Parameters from the server's own tool schema.

WHY IT NEEDS A POLICY

Why email_mark_read needs a policy

This tool modifies email state (marking as read) but is reversible—the user can mark it unread again. It does not delete, destroy, execute arbitrary code, move money, or retrieve sensitive data beyond access already granted. The blast radius is minimal: an agent misusing this would only toggle email read status, causing minor organizational disruption.

From the tool's definition Tool name 'email_mark_read' and description 'Mark an email as read' indicate modification of email metadata/state. The action changes the read status flag of an email.

Risk signalsAccepts file system path (folder) · Handles credentials or secrets (password)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

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.

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

FAQ

Questions about email_mark_read

What does the email_mark_read tool do? +

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

What parameters does email_mark_read accept? +

email_mark_read accepts 4 parameters: uid, email, folder, password. Required: uid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on email_mark_read? +

Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.