Create a new custom workflow from YAML definition. The YAML will be validated before deployment.
AI agents use create_custom_workflow 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 tool creates and deploys a new workflow configuration, which is a reversible write operation that modifies system state. The severity is high because a malicious workflow could be used to orchestrate harmful actions across Kubernetes/cloud environments (given the security-focused context of RAD Security), but the operation itself is not irreversible (workflows can be deleted/modified) and does not directly…
From the tool's definition Tool name explicitly states 'create_custom_workflow'; description indicates it 'Create[s] a new custom workflow from YAML definition' and deploys it after validation.
Documented attack patterns abuse exactly the kind of access create_custom_workflow 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 create_custom_workflow:
{
"version": "1",
"default": "deny",
"tools": {
"create_custom_workflow": {
"limits": [
{
"counter": "create_custom_workflow_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_custom_workflow 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.
Create a new custom workflow from YAML definition. The YAML will be validated before deployment. 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 create_custom_workflow: 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.
create_custom_workflow 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 create_custom_workflow 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 create_custom_workflow. 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.
create_custom_workflow 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.