Add an emoji reaction to a message.
AI agents use add_reaction 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.
This tool creates new data (a reaction entry) but does not delete, execute arbitrary operations, move money, or cause irreversible damage. Removing a reaction is straightforward and undoes the change. It fits the Write category as a reversible data creation action. Severity is low because reactions have minimal blast radius; the worst impact is minor spam or cluttered messaging experience.
From the tool's definition The tool 'add_reaction' adds an emoji reaction to a message—a straightforward modification of message metadata that is reversible.
Documented attack patterns abuse exactly the kind of access add_reaction 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 add_reaction:
{
"version": "1",
"default": "deny",
"tools": {
"add_reaction": {
"limits": [
{
"counter": "add_reaction_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_reaction 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.
Add an emoji reaction to a message. 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 add_reaction: 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.
add_reaction 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 add_reaction 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 add_reaction. 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.
add_reaction 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.