List flows as a Markdown table (ID | State | Assignee | Titel). Conventions enforced uniformly across the plugin (skill: devflow-flow-display): - ⭐ prefix marks flows assigned to / created by the current user - 🔒 marks active agent sessions; idle flows have no lock-marker - Done-flows are hidden...
AI agents call flow_list to retrieve information from DevFlow MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
flow_list retrieves and displays flow information in a read-only manner. It queries existing flow data (ID, State, Assignee, Title) with optional filtering (includeDone parameter) but produces no side effects, modifications, or state changes. This is a straightforward data retrieval operation with minimal risk if misused by an AI agent.
From the tool's definition Tool description states 'List flows as a Markdown table' and the rationale emphasizes retrieval use cases: 'Use this to find flows to work on or to brief the user on the backlog.' No creation, modification, or deletion of data occurs.
Attacks that exploit this kind of access
List flows as a Markdown table (ID | State | Assignee | Titel). Conventions enforced uniformly across the plugin (skill: devflow-flow-display): - ⭐ prefix marks flows assigned to / created by the current user - 🔒 marks active agent sessions; idle flows have no lock-marker - Done-flows are hidden by default (focus on open work). Pass includeDone=true to see them. - Order matches the browser FlowsPage default (kanban_sort_order ASC for project-scope, updated_at DESC for cross-project). Use this to find flows to work on or to brief the user on the backlog. It is categorised as a Read tool in the DevFlow MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for flow_list: 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_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the flow_list 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_list. 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_list 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 →