Get all events from a session with optional filtering by event type
AI agents call get_session_events to retrieve information from OpenReplay MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves session event data without creating, modifying, deleting, or executing operations. It is purely informational, fitting the Read category. Severity is low as retrieval of analytics data poses minimal risk even if misused by an agent—no data is altered, deleted, or financial commitments made.
From the tool's definition Tool name 'get_session_events' and description 'Get all events from a session with optional filtering by event type' indicate a retrieval operation. The verb 'Get' and phrase 'optional filtering' confirm data querying with no modifications or side effects.
Attacks that exploit this kind of access
Get all events from a session with optional filtering by event type. It is categorised as a Read tool in the OpenReplay MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenReplay MCP Server MCP server in PolicyLayer and add a rule for get_session_events: 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 OpenReplay MCP Server. Nothing to install.
get_session_events 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_events 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_events. 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_events is provided by the OpenReplay MCP Server MCP server (lekt9/openreplay-mcp). 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 →