Get full details for a specific visitor session, including pages, events, device context, errors, and friction signals.
AI agents call get_session_detail 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 |
|---|---|---|---|
session_id | string | Yes | Session primary key from get_sessions. |
Parameters from the server's own tool schema.
This tool retrieves sensitive visitor session data including browsing behavior, events, device information, and errors. While it is a read-only operation (no side effects), the severity is high because session replay data can expose personally identifiable information (PII), passwords, sensitive form inputs, and detailed user behavior patterns.
From the tool's definition Tool name 'get_session_detail' and description 'Get full details for a specific visitor session, including pages, events, device context, errors, and friction signals' indicate retrieval of session data with no modification capability.
Attacks that exploit this kind of access
Get full details for a specific visitor session, including pages, events, device context, errors, and friction signals. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_session_detail accepts 1 parameter: session_id. Required: session_id. 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_session_detail: 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_session_detail 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_session_detail 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_session_detail. 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_session_detail 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 →