List recent visitor sessions with filters for URL, country, device, duration, friction, and rage clicks.
AI agents call get_sessions 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. |
query | string | — | Search entry or exit URLs, for example /pricing. |
offset | integer | — | Pagination offset. |
country | string | — | Country name filter. |
device_type | string | — | Device type filter. |
min_duration | integer | — | Minimum session duration in seconds. |
min_friction | integer | — | Minimum friction score. |
has_rage_clicks | boolean | — | Only sessions with rage clicks. |
Parameters from the server's own tool schema.
This is a pure read operation that queries analytics data. No side effects, no state changes, no code execution. The sibling tools (get_anomalies, get_campaign_roas, get_funnel_analysis, get_live_visitors, get_errors) all follow the 'get_' pattern and are clearly read-only analytics queries.
From the tool's definition Tool name is 'get_sessions' and description explicitly states 'List recent visitor sessions' — retrieves data with no modification or destructive capability.
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
List recent visitor sessions with filters for URL, country, device, duration, friction, and rage clicks. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_sessions accepts 8 parameters: limit, query, offset, country, device_type, min_duration, min_friction, has_rage_clicks. 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_sessions: 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_sessions 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_sessions 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_sessions. 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_sessions 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 →