This record as markdown: /tools/io-github-ruvnet-claude-flow/create-workflow.md
What create-workflow does on Claude Flow
AI agents use create-workflow to create or update resources in Claude Flow, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Flow environment.
Why create-workflow is rated Medium
Creating a workflow is a reversible write operation—new workflows can be deleted or modified post-creation. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial).
From the tool's definition Tool name 'create-workflow' and description 'Create a new workflow' indicate data creation. Lacks specificity on what 'workflow' means or whether execution is automatic, but the verb 'create' clearly signals a write operation that modifies system state.
Attacks that exploit this kind of access
The rule that runs create-workflow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Flow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For create-workflow, this is the rule to start with:
create-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.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every create-workflow call is checked against it from then on.
Questions about create-workflow
Create a new workflow. It is categorised as a Write tool in the Claude Flow MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Flow MCP server in PolicyLayer and add a rule for create-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 Claude Flow. Nothing to install.
create-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-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-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-workflow is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claude Flow, and thousands of servers like it.
This server
Across the catalogue