Get cumulative scroll-depth reach buckets for a specific page path.
AI agents call get_scroll_depth 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. |
path | string | Yes | Page path to analyze, for example /pricing. |
Parameters from the server's own tool schema.
This tool retrieves analytics data (scroll depth metrics for a page) with no capability to modify, delete, or execute operations. It is purely observational data access, consistent with the Read category. Severity is low because misuse would only expose analytics insights, not endanger data integrity or cause operational harm.
From the tool's definition Tool name 'get_scroll_depth' and description 'Get cumulative scroll-depth reach buckets' indicate retrieval of analytics metrics without modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
Get cumulative scroll-depth reach buckets for a specific page path. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_scroll_depth accepts 2 parameters: days, path. Required: path. 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_scroll_depth: 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_scroll_depth 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_scroll_depth 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_scroll_depth. 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_scroll_depth 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 →