List all active sessions in the system (admin).
AI agents call list_all_sessions to retrieve information from Kasm MCP Server v2 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves session data without creating, modifying, or deleting anything. It is a Read operation. Severity is medium rather than low because the data retrieved (all active sessions) could include sensitive information about system usage, user activity, and active infrastructure that an adversary could leverage for reconnaissance or privilege escalation planning.
From the tool's definition Tool name and description indicate it 'List all active sessions' — a retrieval operation with no data modification. The (admin) qualifier confirms it requires elevated privileges but does not change the nature of the action.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
List all active sessions in the system (admin). It is categorised as a Read tool in the Kasm MCP Server v2 MCP Server, which means it retrieves data without modifying state.
Register the Kasm MCP Server v2 MCP server in PolicyLayer and add a rule for list_all_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 Kasm MCP Server v2. Nothing to install.
list_all_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_all_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_all_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_all_sessions is provided by the Kasm MCP Server v2 MCP server (roguedev-ai/kasm-mcp-server-v2). 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 →