Удалить отложенные сообщения (до их отправки).
AI agents call delete_scheduled to permanently remove resources in Claudegram — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes scheduled messages from a Telegram account. Deletion is an irreversible operation that cannot be undone, matching the Destructive category definition. While the blast radius is somewhat limited to the user's own scheduled messages (not system-wide), the irreversible nature and the sensitive context of personal communications elevates this to high severity.
From the tool's definition Tool name 'delete_scheduled' and description 'Удалить отложенные сообщения (до их отправки)' which translates to 'Delete scheduled messages (before they are sent)' explicitly performs irreversible deletion of data.
Attacks that exploit this kind of access
Удалить отложенные сообщения (до их отправки). It is categorised as a Destructive tool in the Claudegram MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claudegram MCP server in PolicyLayer and add a rule for delete_scheduled: 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 Claudegram. Nothing to install.
delete_scheduled 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 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. 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 is provided by the Claudegram MCP server (sanjar-x/claudegram). 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 →