Get list of Kasm users.
AI agents call get_kasm_users 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 retrieves user information from the Kasm system without creating, modifying, deleting, or executing any operations. It is purely informational and poses minimal risk if misused by an AI agent—the worst outcome would be unauthorized enumeration of users, which is a low-severity information disclosure concern.
From the tool's definition Tool name 'get_kasm_users' and description 'Get list of Kasm users' indicate a retrieval operation with no side effects. The verb 'Get' and lack of any modification, deletion, or execution language confirms this is a read-only query.
Attacks that exploit this kind of access
Get list of Kasm users. 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 get_kasm_users: 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.
get_kasm_users 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 get_kasm_users 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 get_kasm_users. 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.
get_kasm_users 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 →