[Requires userId with API key auth] Search and filter sessions. Full search requires JWT authentication.
AI agents call search_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 and queries session data based on filter criteria. It performs read-only operations without creating, modifying, deleting, or executing code. The authentication requirement (userId, API key, JWT) is a security control but does not elevate the risk category beyond Read.
From the tool's definition Tool is named 'search_sessions' and described as 'Search and filter sessions' with no modification, deletion, or execution capabilities mentioned. The description explicitly states it searches and filters—retrieval operations with no side effects.
Attacks that exploit this kind of access
[Requires userId with API key auth] Search and filter sessions. Full search requires JWT authentication. 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 search_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.
search_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 search_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 search_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.
search_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 →