[Notifications] Get notification counts by type/severity.
AI agents call notifications_get_counts to retrieve information from CyPerf MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and reports aggregated notification counts—a read-only query operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal; an agent retrieving notification counts cannot cause damage or unintended state changes.
From the tool's definition Tool name 'notifications_get_counts' and description 'Get notification counts by type/severity' indicate a retrieval operation that queries existing notification data without modifying, deleting, or executing any actions.
Attacks that exploit this kind of access
[Notifications] Get notification counts by type/severity. It is categorised as a Read tool in the CyPerf MCP Server MCP Server, which means it retrieves data without modifying state.
Register the CyPerf MCP Server MCP server in PolicyLayer and add a rule for notifications_get_counts: 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 CyPerf MCP Server. Nothing to install.
notifications_get_counts 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 notifications_get_counts 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 notifications_get_counts. 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.
notifications_get_counts is provided by the CyPerf MCP Server MCP server (keysight/cyperf-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 →