🕐 Schedule a deployment to run at specific times or intervals. Set up automated execution of deployments using flexible scheduling options including: - One-time execution at a specific date/time - Recurring schedules using cron expressions - Simple interval-based schedules (daily, weekly, monthl...
Risk signalsHigh parameter count (13 properties)
Part of the DataGen server.
Free to start. No card required.
AI agents use scheduleDeployment to create or modify resources in DataGen. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call scheduleDeployment repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach DataGen.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"scheduleDeployment": {
"limits": [
{
"counter": "scheduledeployment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full DataGen policy for all 20 tools.
These attack patterns abuse exactly the kind of access scheduleDeployment gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
🕐 Schedule a deployment to run at specific times or intervals. Set up automated execution of deployments using flexible scheduling options including: - One-time execution at a specific date/time - Recurring schedules using cron expressions - Simple interval-based schedules (daily, weekly, monthly) Perfect for: - Automated data processing workflows - Regular report generation - Periodic API data syncing - Scheduled backup operations - Time-based business process automation Schedule Types: - 'once': Execute once at a specific datetime - 'cron': Use cron expression for complex schedules - 'interval': Simple recurring intervals (daily, weekly, monthly) Examples: - Daily at 9 AM: schedule_type='interval', interval='daily', time='09:00' - Every Monday at 2 PM: schedule_type='cron', cron_expression='0 14 * * 1' - Once on Dec 25, 2024 at 10:30 AM: schedule_type='once', datetime='2024-12-25T10:30:00Z'. It is categorised as a Write tool in the DataGen MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DataGen MCP server in PolicyLayer and add a rule for scheduleDeployment: 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.
scheduleDeployment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the scheduleDeployment 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 scheduleDeployment. 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.
scheduleDeployment 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.