zulip_update_message_flags · Zulip MCP Server MCP

WHAT IT DOES

What zulip_update_message_flags does on Zulip MCP Server

AI agents use zulip_update_message_flags 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_update_message_flags needs a policy

This tool modifies message metadata (flags) in a reversible manner. Adding or removing flags like 'read' or 'starred' changes the state of messages but does not create, delete, or execute operations. It is Write-category because it modifies data reversibly.

From the tool's definition Tool name is 'zulip_update_message_flags' with description 'Add or remove flags (read, starred, etc.) on messages'. The verbs 'add' and 'remove' indicate modification of message metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

zulip_update_message_flags Rate-limited

zulip_update_message_flags 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_update_message_flags": {
      "limits": [
        {
          "counter": "zulip_update_message_flags_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_update_message_flags

What does the zulip_update_message_flags tool do? +

Add or remove flags (read, starred, etc.) on messages. 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_update_message_flags? +

Register the Zulip MCP Server MCP server in PolicyLayer and add a rule for zulip_update_message_flags: 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_update_message_flags? +

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

Can I rate-limit zulip_update_message_flags? +

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

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

zulip_update_message_flags 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.