Add a cron-based schedule to a workflow. The schedule will trigger the workflow automatically at the specified times.
AI agents use add_workflow_schedule to create or update resources in RAD Security — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your RAD Security environment.
This is a Write operation because it creates or modifies workflow configuration reversibly—adding a schedule changes how and when a workflow executes, but the action can be undone by removing the schedule. It is not Execute because it does not run the workflow itself or trigger external operations directly.
From the tool's definition The tool 'add_workflow_schedule' modifies workflow configuration by adding a cron-based schedule, which creates a new recurring trigger.
Documented attack patterns abuse exactly the kind of access add_workflow_schedule gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RAD Security, and nothing reaches the server without passing your rules. This is the rule we recommend for add_workflow_schedule:
{
"version": "1",
"default": "deny",
"tools": {
"add_workflow_schedule": {
"limits": [
{
"counter": "add_workflow_schedule_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_workflow_schedule stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Add a cron-based schedule to a workflow. The schedule will trigger the workflow automatically at the specified times. It is categorised as a Write tool in the RAD Security MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RAD Security MCP server in PolicyLayer and add a rule for add_workflow_schedule: 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 RAD Security. Nothing to install.
add_workflow_schedule 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 add_workflow_schedule 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 add_workflow_schedule. 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.
add_workflow_schedule is provided by the RAD Security MCP server (rad-security/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from RAD Security, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
55 RAD Security tools catalogued and risk-classified — across an index of 43,000+ MCP servers.