Get errors and issues with their impact and affected sessions
AI agents call get_errors_issues 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 error/issue data from OpenReplay sessions—a read-only operation with no ability to modify, delete, or execute actions. It fits the Read category (search, list, get, fetch). Severity is low because the blast radius of misuse is limited to information disclosure of analytics data that is typically already visible to authorized users within the platform.
From the tool's definition Tool name 'get_errors_issues' and description 'Get errors and issues with their impact and affected sessions' indicates data retrieval only. Verb 'Get' and passive framing ('with their impact') show no side effects or modifications.
Attacks that exploit this kind of access
Get errors and issues with their impact and affected 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_errors_issues: 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_errors_issues 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_errors_issues 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_errors_issues. 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_errors_issues 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 →