Subscribe to a Zulip stream. Creates the stream if it does not exist.
AI agents use zulip_subscribe_to_stream 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.
This tool modifies state by subscribing the user/agent to a stream and may create streams as a side effect. These are write operations because they create or modify data (stream creation and subscription records) in a reversible manner.
From the tool's definition The tool description explicitly states it 'Subscribe to a Zulip stream. Creates the stream if it does not exist.' This involves creating new resources (streams) and modifying subscription state, which are reversible write operations.
Attacks that exploit this kind of access
Subscribe to a Zulip stream. Creates the stream if it does not exist. 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.
Register the Zulip MCP Server MCP server in PolicyLayer and add a rule for zulip_subscribe_to_stream: 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.
zulip_subscribe_to_stream is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the zulip_subscribe_to_stream 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.
Set action: deny in the PolicyLayer policy for zulip_subscribe_to_stream. 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.
zulip_subscribe_to_stream 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →