mark_messages_as_seen · Multilead Open API MCP Server MCP

WHAT IT DOES

What mark_messages_as_seen does on Multilead Open API MCP Server

AI agents use mark_messages_as_seen to create or update resources in Multilead Open API MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Multilead Open API MCP Server environment.

WHY IT NEEDS A POLICY

Why mark_messages_as_seen needs a policy

This tool modifies message metadata (seen status) without deleting or creating new records. It is reversible (messages can be marked unseen or seen again). While it affects system state, the change is non-destructive and does not execute external code or commands. This fits the Write category (modifies data reversibly).

From the tool's definition The tool description states 'Mark messages in a thread as seen', which modifies the read/seen status of messages—a reversible state change to data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

mark_messages_as_seen Rate-limited

mark_messages_as_seen 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_messages_as_seen": {
      "limits": [
        {
          "counter": "mark_messages_as_seen_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 Multilead Open API MCP Server, so you can run agents against it safely.

FAQ

Questions about mark_messages_as_seen

What does the mark_messages_as_seen tool do? +

Mark messages in a thread as seen. It is categorised as a Write tool in the Multilead Open API 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 mark_messages_as_seen? +

Register the Multilead Open API MCP Server MCP server in PolicyLayer and add a rule for mark_messages_as_seen: 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 Multilead Open API MCP Server. Nothing to install.

What risk level is mark_messages_as_seen? +

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

Can I rate-limit mark_messages_as_seen? +

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

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

mark_messages_as_seen is provided by the Multilead Open API MCP Server MCP server (vanman2024/multilead-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.