Get session recordings for a specific Kasm session.
AI agents call get_session_recordings 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 session recordings, which is a query/fetch operation with no side effects. However, the severity is elevated to 'medium' rather than 'low' because session recordings may contain sensitive information (user activity, screen captures, credentials, proprietary data) that could be exposed if an AI agent gains unauthorized access to retrieve them.
From the tool's definition Tool name 'get_session_recordings' and description 'Get session recordings for a specific Kasm session' indicate retrieval of data with no modification or execution.
Attacks that exploit this kind of access
Get session recordings for a specific 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 get_session_recordings: 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_session_recordings 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_session_recordings 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_session_recordings. 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_session_recordings 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 →