Get currently active visitors and sessions seen in the live activity window.
AI agents call get_live_visitors 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.
This tool retrieves real-time visitor and session information from an analytics platform. It performs no write, execute, or destructive operations—it merely reads and returns current session data. The data returned is informational analytics that cannot be modified or acted upon through this tool alone. Blast radius of misuse is limited to information disclosure about visitor traffic patterns.
From the tool's definition Tool name 'get_live_visitors' and description 'Get currently active visitors and sessions seen in the live activity window' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
Get currently active visitors and sessions seen in the live activity window. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
Register the KrystalView Analytics MCP server in PolicyLayer and add a rule for get_live_visitors: 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_live_visitors 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_live_visitors 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_live_visitors. 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_live_visitors 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 →