Create a new workflow run in draft status.
AI agents use create_workflow_run to create or update resources in Dag Planner — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dag Planner environment.
This tool creates a new workflow run record in draft status, which is a reversible write operation. It does not execute tasks, delete data, or move money. The severity is medium because creating workflow runs could consume resources or trigger downstream automation if not properly constrained, but the draft status suggests it's not immediately active.
From the tool's definition Tool name 'create_workflow_run' and description 'Create a new workflow run in draft status' indicates creation of a new data entity.
Attacks that exploit this kind of access
Create a new workflow run in draft status. It is categorised as a Write tool in the Dag Planner MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dag Planner MCP server in PolicyLayer and add a rule for create_workflow_run: 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 Dag Planner. Nothing to install.
create_workflow_run 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_run 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_run. 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_run is provided by the Dag Planner MCP server (shubhamnegi/dag-planner-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →