React to a Rocket.Chat message with an emoji. Use this to
AI agents use add_reaction to create or update resources in Rocket Cli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Rocket Cli environment.
Adding a reaction modifies message state in Rocket.Chat by associating an emoji reaction with a message and user. This is a non-destructive write operation (reactions can be removed/changed). It has no financial impact, doesn't execute external code, and doesn't delete data. The blast radius is minimal—an agent could clutter chat with unwanted reactions, but the impact is easily reversible and low-severity.
From the tool's definition Tool description states 'React to a Rocket.Chat message with an emoji.' This creates/modifies reaction metadata on an existing message, which is a reversible write operation.
Attacks that exploit this kind of access
React to a Rocket.Chat message with an emoji. Use this to. It is categorised as a Write tool in the Rocket Cli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Rocket Cli 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 Rocket Cli. 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 Rocket Cli MCP server (jeanfbrito/rocket-cli). 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 →