🗑️ Delete a scheduled deployment permanently. Remove a scheduled deployment from the system. This action cannot be undone, but it will not affect any deployments that have already been executed. Perfect for: - Removing schedules that are no longer needed - Cleaning up test or temporary schedules...
Part of the DataGen server.
Free to start. No card required.
AI agents may call deleteSchedule to permanently remove or destroy resources in DataGen. Without a policy, an autonomous agent could delete critical data in a loop with no way to undo the damage. PolicyLayer blocks destructive tools by default and requires explicit human approval before enabling them.
Without a policy, an AI agent could call deleteSchedule in a loop, permanently destroying resources in DataGen. There is no undo for destructive operations. PolicyLayer blocks this tool by default and only allows it when a human explicitly approves the action.
Destructive tools permanently remove data. Block by default. Only enable with explicit approval workflows.
{
"version": "1",
"default": "deny",
"hide": [
"deleteSchedule"
]
}See the full DataGen policy for all 20 tools.
These attack patterns abuse exactly the kind of access deleteSchedule gives an agent. Each links to the full case and the policy that stops it:
Other destructive tools across the catalogue. The same approach applies to each: deny by default, or require human approval.
🗑️ Delete a scheduled deployment permanently. Remove a scheduled deployment from the system. This action cannot be undone, but it will not affect any deployments that have already been executed. Perfect for: - Removing schedules that are no longer needed - Cleaning up test or temporary schedules - Managing schedule cleanup and maintenance Warning: This action is permanent and cannot be undone.. It is categorised as a Destructive tool in the DataGen MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DataGen MCP server in PolicyLayer and add a rule for deleteSchedule: 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 DataGen. Nothing to install.
deleteSchedule 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 deleteSchedule 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 deleteSchedule. 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.
deleteSchedule is provided by the DataGen MCP server (kuoyusheng/datagendev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 DataGen tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.