Delete scheduled SMS message(s)
AI agents call delete_sms to permanently remove resources in Seven — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes scheduled SMS messages, which cannot be undone. Deletion operations fall into the Destructive category. The severity is high because an AI agent misusing this could delete important scheduled communications without recovery, impacting business operations and customer communication. The confidence is high due to explicit 'delete' language in both name and description.
From the tool's definition Tool name is 'delete_sms' and description states 'Delete scheduled SMS message(s)'. The word 'Delete' combined with the action of removing scheduled SMS messages indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete scheduled SMS message(s). It is categorised as a Destructive tool in the Seven MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Seven MCP server in PolicyLayer and add a rule for delete_sms: 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 Seven. Nothing to install.
delete_sms 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_sms 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_sms. 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_sms is provided by the Seven MCP server (seven-io/seven-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 →