Add an emoji reaction to a message
AI agents use zulip_add_reaction 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.
Adding a reaction creates new data (the reaction association) in a reversible manner. Users can remove reactions, and the action does not delete, execute code, move funds, or trigger external operations. This is a standard Write operation with minimal blast radius—reactions are cosmetic metadata with no side effects on message content or system state.
From the tool's definition Tool name 'zulip_add_reaction' and description 'Add an emoji reaction to a message' indicate creation of a new reaction entity (emoji metadata attached to a message).
Attacks that exploit this kind of access
Add an emoji reaction to a message. 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_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 MCP Server. Nothing to install.
zulip_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 zulip_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 zulip_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.
zulip_add_reaction 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 →