List iMessage conversations, sorted by most recent activity.
AI agents call list_chats to retrieve information from Bluebubbles without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing iMessage conversations without creating, modifying, deleting, or executing any operations. It is a read-only operation that simply enumerates data. While the data retrieved (iMessage conversations) may contain sensitive personal information, the tool itself performs no destructive or side-effect-producing action.
From the tool's definition Tool name 'list_chats' and description 'List iMessage conversations, sorted by most recent activity' indicate a query/retrieval operation with no data modification or execution of external commands.
Attacks that exploit this kind of access
List iMessage conversations, sorted by most recent activity. It is categorised as a Read tool in the Bluebubbles MCP Server, which means it retrieves data without modifying state.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for list_chats: 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.
list_chats is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_chats 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 list_chats. 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.
list_chats 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 →