daa_workflow_create · Claude Flow MCP: Risk & Policy

WHAT IT DOES

What daa_workflow_create does on Claude Flow

AI agents use daa_workflow_create 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 IT NEEDS A POLICY

Why daa_workflow_create needs a policy

This tool creates a new workflow object in the system, which is a reversible write operation. The 'autonomous' and 'swarm' context suggests it may spawn or configure agents, but the primary action described is workflow creation, not execution of external code or deletion.

From the tool's definition Tool name contains 'create' and description states 'Create an autonomous workflow'; this is a creation action that modifies system state by adding a new workflow entity.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

daa_workflow_create Rate-limited

daa_workflow_create 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "daa_workflow_create": {
      "limits": [
        {
          "counter": "daa_workflow_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Claude Flow, so you can run agents against it safely.

FAQ

Questions about daa_workflow_create

What does the daa_workflow_create tool do? +

Create an autonomous workflow Use when native Task is wrong because you need agents that adapt their cognitive pattern (convergent / divergent / lateral / systems / critical) per-task and share knowledge across the swarm. For static one-shot agents, native Task is fine. 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.

How do I enforce a policy on daa_workflow_create? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for daa_workflow_create: 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.

What risk level is daa_workflow_create? +

daa_workflow_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit daa_workflow_create? +

Yes. Add a rate_limit block to the daa_workflow_create 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.

How do I block daa_workflow_create completely? +

Set action: deny in the PolicyLayer policy for daa_workflow_create. 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.

What MCP server provides daa_workflow_create? +

daa_workflow_create 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.