Get sessions for a specific user ID (API key authentication supported)
AI agents call get_user_sessions 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 information for a user—a pure read operation with no side effects. However, severity is medium rather than low because the data retrieved (user sessions) is sensitive behavioral and interaction data that could expose personal user patterns, navigation history, and potentially private information if accessed by an unauthorized agent.
From the tool's definition Tool name 'get_user_sessions' and description 'Get sessions for a specific user ID' indicate data retrieval with no modification or deletion. The server's purpose is analytics and querying user session data, which are inherently read operations.
Attacks that exploit this kind of access
Get sessions for a specific user ID (API key authentication supported). 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_user_sessions: 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_user_sessions 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_user_sessions 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_user_sessions. 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_user_sessions 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 →