Create a new flow in a project. Use this to create new feature requests, bug reports, or tasks. The flow starts in
AI agents use flow_create to create or update resources in DevFlow MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DevFlow MCP Server environment.
This tool creates new records (flows/feature requests/bug reports/tasks) in a project management system, which is a reversible write operation. While it doesn't execute code or delete data, creating many flows could clutter the system, and improper use could generate noise or false workflows.
From the tool's definition Tool description states 'Create a new flow in a project' and 'Use this to create new feature requests, bug reports, or tasks.' The verb 'Create' and explicit mention of creating new items indicates data creation.
Attacks that exploit this kind of access
Create a new flow in a project. Use this to create new feature requests, bug reports, or tasks. The flow starts in. It is categorised as a Write tool in the DevFlow MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for flow_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 DevFlow MCP Server. Nothing to install.
flow_create 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 flow_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.
Set action: deny in the PolicyLayer policy for flow_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.
flow_create is provided by the DevFlow MCP Server MCP server (klausfreiberufler/devflow-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 →