List detected traffic, friction, bounce, and conversion anomalies for the site.
AI agents call get_anomalies 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. |
unacknowledged_only | boolean | — | Only include unacknowledged anomalies. |
Parameters from the server's own tool schema.
This tool queries and returns analytics data (anomalies) without creating, modifying, deleting, or executing anything. It has no side effects beyond data retrieval. The blast radius of misuse is minimal—an agent might retrieve sensitive business metrics, but cannot alter systems, trigger actions, or cause irreversible harm.
From the tool's definition Tool name 'get_anomalies' and description 'List detected traffic, friction, bounce, and conversion anomalies' indicate a retrieval operation.
Attacks that exploit this kind of access
List detected traffic, friction, bounce, and conversion anomalies for the site. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_anomalies accepts 2 parameters: limit, unacknowledged_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_anomalies: 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_anomalies 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_anomalies 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_anomalies. 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_anomalies 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 →