mark_message_read · Coord MCP: Risk & Policy

WHAT IT DOES

What mark_message_read does on CoordMCP

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

WHY IT NEEDS A POLICY

Why mark_message_read needs a policy

The name 'mark_message_read' strongly suggests it updates the read/seen status of a message, which is a lightweight, reversible write operation (toggling a flag). This is consistent with the server's shared memory and coordination purpose. No description is available to confirm or contradict this interpretation, so confidence is reduced. It does not appear destructive, financial, or execute-level.

From the tool's definition Tool name: mark_message_read — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_message_read Rate-limited

mark_message_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": {
    "mark_message_read": {
      "limits": [
        {
          "counter": "mark_message_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 CoordMCP, so you can run agents against it safely.

FAQ

Questions about mark_message_read

What does the mark_message_read tool do? +

mark_message_read. It is categorised as a Write tool in the CoordMCP 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_message_read? +

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

What risk level is mark_message_read? +

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

Can I rate-limit mark_message_read? +

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

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

mark_message_read is provided by the Coord MCP server (siddiquesahabaj/coordmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.