send_reaction
AI agents use send_reaction to create or update resources in Bluebubbles — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bluebubbles environment.
Sending a reaction is a write operation that creates or modifies message metadata (adds an emoji/reaction to a message) but is reversible and has no destructive or financial impact. The empty description lowers confidence slightly, but context from the server's message management capabilities and sibling tools (edit_message, delete_message) clarifies intent.
From the tool's definition Tool named 'send_reaction' on a BlueBubbles iMessage server; sibling tools show this server modifies messages (edit_message, delete_message, send messages). Reactions are metadata writes to existing messages.
Attacks that exploit this kind of access
send_reaction. It is categorised as a Write tool in the Bluebubbles MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for send_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 Bluebubbles. Nothing to install.
send_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 send_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 send_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.
send_reaction is provided by the Bluebubbles MCP server (metaember/bluebubbles-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 →