List all active sessions for the current user.
AI agents call list_user_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 returns information about existing sessions without creating, modifying, deleting, or executing operations. It is a straightforward read operation with minimal blast radius—the worst outcome of misuse would be information disclosure about the current user's sessions, which is low severity.
From the tool's definition Tool name 'list_user_sessions' and description 'List all active sessions for the current user' indicate a retrieval/query operation with no data modification or side effects.
Attacks that exploit this kind of access
List all active sessions for the current user. 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_user_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_user_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_user_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_user_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_user_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 →