Send a message to a named group chat.
AI agents use send_group_message to create or update resources in iMessage MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your iMessage MCP Server environment.
This tool sends messages to group chats, which creates new data (message records) in the iMessage database. It is reversible (messages can be deleted or edited later) and has no financial impact. While it could be misused to send unwanted messages at scale, the blast radius is limited to messaging operations on a single macOS system.
From the tool's definition Tool name 'send_group_message' and description 'Send a message to a named group chat' indicate this tool creates/modifies data by adding messages to group conversations.
Attacks that exploit this kind of access
Send a message to a named group chat. It is categorised as a Write tool in the iMessage MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the iMessage MCP Server MCP server in PolicyLayer and add a rule for send_group_message: 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 iMessage MCP Server. Nothing to install.
send_group_message 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_group_message 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_group_message. 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_group_message is provided by the iMessage MCP Server MCP server (viraatdas/imessage-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 →