Read a file from a Kasm session.
AI agents call read_kasm_file 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 file contents from a containerized Kasm workspace session. It performs a read operation with no side effects—no data is created, modified, deleted, or executed. The blast radius is limited to information disclosure risk, which is context-dependent but typically lower severity than write/execute/destructive operations. Confidence is high because the description is clear and unambiguous.
From the tool's definition Tool name 'read_kasm_file' and description 'Read a file from a Kasm session' explicitly indicate file retrieval with no modification or deletion.
Attacks that exploit this kind of access
Read a file from a Kasm session. 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 read_kasm_file: 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.
read_kasm_file 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 read_kasm_file 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 read_kasm_file. 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.
read_kasm_file 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 →