create_workflow
Create a new empty workflow with a name and optional description. The workflow will be private by default.
This record as markdown: /tools/flowdot-llc-mcp-server/create-workflow.md
What create_workflow does on FlowDot MCP Server
AI agents use create_workflow to create or update resources in FlowDot MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FlowDot MCP Server environment.
Why create_workflow is rated Medium
Creating a new workflow is a write operation that reversibly adds data to the FlowDot platform. It does not execute arbitrary code, delete data irreversibly, or move money. While it creates new resources, the action is reversible (workflows can be deleted), placing it firmly in the Write category rather than Execute.
From the tool's definition The tool description states it will 'Create a new empty workflow' with a name and optional description, which is a create action that modifies data by adding a new workflow to the system.
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 FlowDot MCP Server, 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 FlowDot MCP Server, apply this rule, and every create_workflow call is checked against it from then on.
Questions about create_workflow
Create a new empty workflow with a name and optional description. The workflow will be private by default. It is categorised as a Write tool in the FlowDot MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the FlowDot MCP Server 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 FlowDot MCP Server. 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 FlowDot MCP Server MCP server (flowdot-llc/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FlowDot MCP Server, and thousands of servers like it.
This server
Across the catalogue