Get aggregate site metrics including sessions, duration, friction, rage clicks, daily counts, device mix, and top pages.
AI agents call get_site_stats 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 |
|---|---|---|---|
days | integer | — | Lookback period in days. |
Parameters from the server's own tool schema.
This tool performs a read-only query of analytics data. It retrieves aggregated, pre-computed metrics without side effects, state changes, or external operations. The severity is low because aggregate analytics data is typically non-sensitive business intelligence, and misuse would only expose existing dashboards accessible to authorized users rather than enable destructive or harmful actions.
From the tool's definition Tool retrieves 'aggregate site metrics' such as 'sessions, duration, friction, rage clicks, daily counts, device mix, and top pages' with no modification or execution capabilities implied.
Attacks that exploit this kind of access
Get aggregate site metrics including sessions, duration, friction, rage clicks, daily counts, device mix, and top pages. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_site_stats accepts 1 parameter: days. 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_site_stats: 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_site_stats 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_site_stats 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_site_stats. 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_site_stats 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 →