Cancel a pending scheduled message. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true.
AI agents call cancel_scheduled to permanently remove resources in TrekMail MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling scheduled messages is a destructive operation that permanently prevents a queued message from being sent. Once cancelled, the scheduled message cannot be recovered. The explicit requirement for a destructive flag in the environment variable confirms the developers classified this as a destructive action.
From the tool's definition Tool explicitly requires TREKMAIL_ALLOW_DESTRUCTIVE=true environment variable, and performs 'cancel' operation on scheduled messages—an irreversible action that destroys pending message sends and cannot be undone.
Attacks that exploit this kind of access
Cancel a pending scheduled message. Requires TREKMAIL_ALLOW_DESTRUCTIVE=true. It is categorised as a Destructive tool in the TrekMail MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TrekMail MCP Server MCP server in PolicyLayer and add a rule for cancel_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 TrekMail MCP Server. Nothing to install.
cancel_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 cancel_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 cancel_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.
cancel_scheduled is provided by the TrekMail MCP Server MCP server (trekmail/mcp-server). 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 →