Analyze user funnels and conversion paths
AI agents call get_funnel_analysis 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 analyzes user behavior data (conversion funnels and paths) from OpenReplay sessions. It performs no side effects—no data is created, modified, or deleted. The worst-case misuse would be unauthorized access to analytics insights, which is a confidentiality concern (low severity) rather than integrity or availability damage.
From the tool's definition Tool name 'get_funnel_analysis' and description 'Analyze user funnels and conversion paths' indicate data retrieval and analysis only.
Attacks that exploit this kind of access
Analyze user funnels and conversion paths. 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_funnel_analysis: 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_funnel_analysis 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_funnel_analysis 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_funnel_analysis. 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_funnel_analysis 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 →