zulip_mark_messages_as_read · Zulip MCP Server MCP

WHAT IT DOES

What zulip_mark_messages_as_read does on Zulip MCP Server

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

WHY IT NEEDS A POLICY

Why zulip_mark_messages_as_read needs a policy

This tool changes metadata about messages (their read/unread status) but does not create, delete, or execute arbitrary operations. The modification is reversible—messages can be marked as unread again. This is a state change operation that qualifies as Write category with low severity, as misuse would only affect the agent's or users' notification/read state without data loss or financial impact.

From the tool's definition Tool name 'zulip_mark_messages_as_read' and description 'Mark one or more messages as read' indicate the tool modifies message state (read status) in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zulip_mark_messages_as_read Rate-limited

zulip_mark_messages_as_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": {
    "zulip_mark_messages_as_read": {
      "limits": [
        {
          "counter": "zulip_mark_messages_as_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 Zulip MCP Server, so you can run agents against it safely.

FAQ

Questions about zulip_mark_messages_as_read

What does the zulip_mark_messages_as_read tool do? +

Mark one or more messages as read. It is categorised as a Write tool in the Zulip 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 zulip_mark_messages_as_read? +

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

What risk level is zulip_mark_messages_as_read? +

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

Can I rate-limit zulip_mark_messages_as_read? +

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

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

zulip_mark_messages_as_read is provided by the Zulip MCP Server MCP server (prixite/zulip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.