session_replay
A read tool on the Looking Glass MCP server.
This record as markdown: /tools/io-github-sahib-sawhney-wh-looking-glass-mcp/session-replay.md
What session_replay does on Looking Glass
AI agents call session_replay to retrieve information from Looking Glass without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
sessionId | string | Yes | Session ID (first 8 chars or full UUID) |
Parameters from the server's own tool schema.
Why session_replay is rated Low
Session replay is fundamentally a read operation that retrieves historical session data for playback/review. However, confidence is lowered to 0.6 due to the empty description—the tool could potentially have side effects (like executing recorded actions) that would elevate it to Execute category. The medium severity reflects that session replay could expose sensitive user data or interactions if misused by an agent.
From the tool's definition Tool name is 'session_replay' with no description provided. Based on name alone, session replay typically retrieves and plays back recorded user interactions or browser session data without modifying it.
Attacks that exploit this kind of access
The rule that runs session_replay safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Looking Glass, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For session_replay, this is the rule to start with:
session_replay is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Looking Glass, apply this rule, and every session_replay call is checked against it from then on.
Questions about session_replay
session_replay is a read tool on the Looking Glass MCP server. It is categorised as a Read tool in the Looking Glass MCP Server, which means it retrieves data without modifying state.
session_replay accepts 1 parameter: sessionId. Required: sessionId. The full parameter table on this page comes from the server's own tool schema.
Register the Looking Glass MCP server in PolicyLayer and add a rule for session_replay: 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 Looking Glass. Nothing to install.
session_replay 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 session_replay 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 session_replay. 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.
session_replay is provided by the Looking Glass MCP server (looking-glass-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Looking Glass, and thousands of servers like it.
This server
Across the catalogue