List all scheduled (future) messages.
AI agents call list_scheduled_messages 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 information about scheduled messages without creating, modifying, deleting, or executing any actions. It has no side effects beyond data retrieval. While BlueBubbles provides sensitive message data, the read-only nature of this specific tool makes it lower severity than the destructive or write operations available on the same server (e.g., delete_message, delete_scheduled_message).
From the tool's definition Tool name 'list_scheduled_messages' and description 'List all scheduled (future) messages' indicate a query operation that retrieves data without modification or execution.
Attacks that exploit this kind of access
List all scheduled (future) messages. 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_scheduled_messages: 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_scheduled_messages 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_scheduled_messages 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_scheduled_messages. 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_scheduled_messages 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 →