AI agents use move_messages to create or update resources in Zulip — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zulip environment.
Moving messages changes their organizational state (stream/topic assignment) and is reversible, placing it in Write rather than Destructive. The empty description lowers confidence slightly, but the name and context of sibling message-manipulation tools (edit_message, add_reaction) clarify intent.
From the tool's definition Tool name 'move_messages' indicates modifying the location/organization of messages within Zulip; sibling tools show message manipulation capabilities (edit_message, add_reaction, get_messages); the action moves messages between streams/topics, which is…
Documented attack patterns abuse exactly the kind of access move_messages gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zulip, and nothing reaches the server without passing your rules. This is the rule we recommend for move_messages:
{
"version": "1",
"default": "deny",
"tools": {
"move_messages": {
"limits": [
{
"counter": "move_messages_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}move_messages 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.
move_messages. It is categorised as a Write tool in the Zulip MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zulip MCP server in PolicyLayer and add a rule for move_messages: 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. Nothing to install.
move_messages 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 move_messages 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 move_messages. 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.
move_messages is provided by the Zulip MCP server (windborne/zulipmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zulip, 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.
27 Zulip tools catalogued and risk-classified — across an index of 43,000+ MCP servers.