Medium Risk

mark_read

Mark an email as read via keyboard shortcut (Shift+i)

Part of the Mcpbrowser server.

mark_read can modify Mcpbrowser data, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE MCPBROWSER →

Free to start. No card required.

AI agents use mark_read to create or modify resources in Mcpbrowser. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call mark_read repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Mcpbrowser.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_read": {
      "limits": [
        {
          "counter": "mark_read_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Mcpbrowser policy for all 29 tools.

Get this rule live on your own Mcpbrowser server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY MCPBROWSER →

View all 29 tools →

These attack patterns abuse exactly the kind of access mark_read gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so mark_read only ever does what you allow.

SECURE MCPBROWSER →

Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the mark_read tool do? +

Mark an email as read via keyboard shortcut (Shift+i). It is categorised as a Write tool in the Mcpbrowser 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_read? +

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

What risk level is mark_read? +

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

Can I rate-limit mark_read? +

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

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

mark_read is provided by the Mcpbrowser MCP server (https://github.com/cherchyk/MCPBrowser/releases/download/v0.3.58/mcpbrowser-0.3.58.mcpb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcpbrowser tool call.

Deterministic rules across all 29 Mcpbrowser tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.