Get detailed information about a specific flow. Returns the full flow including: - Summary and description - Acceptance criteria - Current state - Agent status (if being worked on) - Implementation plan (full content) - Audit info (who created/approved) Use this before starting work on a flow to ...
AI agents call flow_get 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.
This tool retrieves and queries flow information without side effects. It does not create, modify, delete, execute code, or commit financial actions. The blast radius of misuse is minimal—an agent could retrieve sensitive flow details but cannot alter systems or data.
From the tool's definition Tool name 'flow_get' and description 'Get detailed information about a specific flow' indicates a retrieval operation.
Attacks that exploit this kind of access
Get detailed information about a specific flow. Returns the full flow including: - Summary and description - Acceptance criteria - Current state - Agent status (if being worked on) - Implementation plan (full content) - Audit info (who created/approved) Use this before starting work on a flow to understand requirements. 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_get: 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_get 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_get 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_get. 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_get 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 →