find_chats
AI agents call find_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 or queries chat data without modifying, deleting, or executing operations. Despite the empty description, the naming convention ('find_') and context of sibling tools (which include destructive operations like delete_chat and delete_message) strongly suggest this is a read-only search function. Confidence is slightly reduced due to the missing description, but the category assignment is clear.
From the tool's definition Tool name 'find_chats' combined with server description stating it 'enables interaction with iMessage through a BlueBubbles server, allowing users to read, search, and send messages'. The 'find' verb indicates a search/query operation with no side effects.
Attacks that exploit this kind of access
find_chats. 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 find_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.
find_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 find_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 find_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.
find_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 →