List agent sessions for a flow. Returns all sessions with their status, timing, and summary. Use this to review past work sessions on a flow.
AI agents call agent_session_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.
This tool retrieves and returns historical session data without modifying, deleting, or executing any operations. It is a pure read operation used for auditing and review purposes. The 'list' verb and passive 'Returns' language confirm no state changes occur.
From the tool's definition Tool name 'agent_session_list' and description 'List agent sessions for a flow. Returns all sessions with their status, timing, and summary.' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
List agent sessions for a flow. Returns all sessions with their status, timing, and summary. Use this to review past work sessions on a flow. 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 agent_session_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.
agent_session_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 agent_session_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 agent_session_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.
agent_session_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 →