Post a new message to a Zulip channel (stream)
AI agents use zulip_post_message 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 creates new data (a message) in a reversible manner—messages can be edited or deleted afterward by users with appropriate permissions. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'zulip_post_message' and description 'Post a new message to a Zulip channel (stream)' indicate creation of new message content in a shared communication channel.
Documented attack patterns abuse exactly the kind of access zulip_post_message 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_post_message:
{
"version": "1",
"default": "deny",
"tools": {
"zulip_post_message": {
"limits": [
{
"counter": "zulip_post_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}zulip_post_message 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.
Post a new message to a Zulip 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_post_message: 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_post_message 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_post_message 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_post_message. 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_post_message 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.