List capture sessions for a project.
AI agents call list_capture_sessions to retrieve information from Qontinui Web MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about existing capture sessions associated with a project. It performs no modifications, deletions, or execution of external operations. The 'list' verb and retrieval-only nature clearly place it in the Read category, with low severity since listing sessions poses minimal risk even if misused.
From the tool's definition Tool name 'list_capture_sessions' and description 'List capture sessions for a project' indicate a data retrieval operation with no side effects.
Attacks that exploit this kind of access
List capture sessions for a project. It is categorised as a Read tool in the Qontinui Web MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Qontinui Web MCP Server MCP server in PolicyLayer and add a rule for list_capture_sessions: 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 Qontinui Web MCP Server. Nothing to install.
list_capture_sessions 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 list_capture_sessions 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 list_capture_sessions. 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.
list_capture_sessions is provided by the Qontinui Web MCP Server MCP server (qontinui/qontinui-web-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 →