Get recent KrystalView notifications such as insights, setup notices, errors, and anomalies.
AI agents call get_notifications 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. |
unread_only | boolean | — | Only include unread notifications. |
Parameters from the server's own tool schema.
This tool retrieves notification data without creating, modifying, deleting, or executing anything. It has no side effects and returns existing information. The blast radius of misuse is minimal—an agent could access notifications it shouldn't see, but cannot alter analytics data or trigger actions. This is a straightforward Read operation.
From the tool's definition Tool name 'get_notifications' and description 'Get recent KrystalView notifications such as insights, setup notices, errors, and anomalies' indicate a read-only retrieval operation.
Attacks that exploit this kind of access
Get recent KrystalView notifications such as insights, setup notices, errors, and anomalies. It is categorised as a Read tool in the KrystalView Analytics MCP Server, which means it retrieves data without modifying state.
get_notifications accepts 2 parameters: limit, unread_only. 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_notifications: 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_notifications 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_notifications 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_notifications. 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_notifications 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 →