Get all sessions for a specific user to analyze behavior patterns.
AI agents call get_user_session_history to retrieve information from OpenReplay Session Analysis 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 historical session data for analysis purposes without creating, modifying, deleting, or executing any operations. It is a straightforward data retrieval function that returns existing session records.
From the tool's definition Tool name 'get_user_session_history' and description 'Get all sessions for a specific user to analyze behavior patterns' indicate data retrieval with no modification. The verb 'get' and the phrase 'to analyze' denote a read-only query operation.
Attacks that exploit this kind of access
Get all sessions for a specific user to analyze behavior patterns. It is categorised as a Read tool in the OpenReplay Session Analysis MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenReplay Session Analysis MCP Server MCP server in PolicyLayer and add a rule for get_user_session_history: 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 Session Analysis MCP Server. Nothing to install.
get_user_session_history 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_session_history 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_session_history. 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_session_history is provided by the OpenReplay Session Analysis MCP Server MCP server (rsp2k/openreplay-mcp-server). 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 →