Subscribe the bot to a channel (stream)
AI agents use zulip_subscribe_to_channel 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.
Subscribing to a channel is a reversible write action — it adds the bot as a member of a stream. This creates a new subscription record but does not delete data, execute code, or involve financial operations. Misuse has limited blast radius as it only affects channel membership for the bot account.
From the tool's definition Subscribe the bot to a channel (stream)
Documented attack patterns abuse exactly the kind of access zulip_subscribe_to_channel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zulip MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for zulip_subscribe_to_channel:
{
"version": "1",
"default": "deny",
"tools": {
"zulip_subscribe_to_channel": {
"limits": [
{
"counter": "zulip_subscribe_to_channel_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} zulip_subscribe_to_channel 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.
Free to start. No card required.
Subscribe the bot to a channel (stream). 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_channel: 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_channel 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_channel 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_channel. 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_channel is provided by the Zulip MCP Server MCP server (monadical-sas/zulip-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zulip MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
8 Zulip MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.