Delete a scheduled message.
AI agents call delete_scheduled_message to permanently remove resources in Bluebubbles — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of data (scheduled messages) cannot be undone. Even though the message was not yet sent, removing it from the schedule is a destructive operation. The impact is high because an AI agent could maliciously delete important scheduled communications, causing communication failures or missed time-sensitive information delivery.
From the tool's definition Tool name contains 'delete' and description states 'Delete a scheduled message' — this irreversibly removes a message that was queued for future sending.
Attacks that exploit this kind of access
Delete a scheduled message. It is categorised as a Destructive tool in the Bluebubbles MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Bluebubbles MCP server in PolicyLayer and add a rule for delete_scheduled_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 Bluebubbles. Nothing to install.
delete_scheduled_message is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_scheduled_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 delete_scheduled_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.
delete_scheduled_message 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 →