Get the complete journey of a user across multiple sessions
AI agents call get_user_journey 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 exclusively queries and retrieves historical user journey data. It has no side effects, cannot modify data, execute code, or trigger external operations. The blast radius of misuse is minimal — an agent could retrieve sensitive session data, but cannot alter system state. Classified as Read with low severity.
From the tool's definition Tool retrieves 'complete journey of a user across multiple sessions' — a query operation with no modification, deletion, or execution capability. Verb 'Get' and passive data retrieval pattern.
Attacks that exploit this kind of access
Get the complete journey of a user across multiple sessions. 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_journey: 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_journey 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_journey 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_journey. 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_journey 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 →