Check a contact's Focus / Do Not Disturb status, if they share it.
AI agents call get_focus_status 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 publicly shared privacy status information about a contact. It performs no side effects, creates no data, executes no code, and cannot damage or delete anything. The operation is a simple information query, making it a Read category tool with low severity since misuse would only expose already-shared status information.
From the tool's definition Tool name 'get_focus_status' and description 'Check a contact's Focus / Do Not Disturb status' indicate a read-only query operation that retrieves status information without modifying any data or triggering actions.
Attacks that exploit this kind of access
Check a contact's Focus / Do Not Disturb status, if they share it. 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 get_focus_status: 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.
get_focus_status 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 get_focus_status 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 get_focus_status. 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.
get_focus_status 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 →