Get aggregated browser errors grouped by type and message, with affected paths and sample sessions.
AI agents call get_errors to retrieve information from KrystalView Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Maximum results to return. |
error_type | string | — | Filter by error type. |
unresolved_only | boolean | — | Only include unresolved errors. |
Parameters from the server's own tool schema.
This tool retrieves and aggregates existing browser error data for analysis purposes. It has no side effects—it does not execute code, modify data, delete information, or trigger external actions. The primary risk is data exposure of error logs and sample session identifiers, which is typical for analytics tools.
From the tool's definition Tool description uses 'Get' and describes retrieval of 'aggregated browser errors' with no modification, deletion, or execution capabilities mentioned. Sibling tools are all read-only analytics queries (get_anomalies, get_campaign_roas, get_live_visitors, etc.
Attacks that exploit this kind of access
Get aggregated browser errors grouped by type and message, with affected paths and sample sessions. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_errors accepts 3 parameters: limit, error_type, unresolved_only. The full parameter table on this page comes from the server's own tool schema.
Register the KrystalView Analytics MCP server in PolicyLayer and add a rule for get_errors: 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 KrystalView Analytics. Nothing to install.
get_errors 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 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. 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 is provided by the KrystalView Analytics MCP server (KrystalView/krystalview-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 →