get_unread_notification_count

What get_unread_notification_count does on Huly

AI agents call get_unread_notification_count to retrieve information from Huly without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_unread_notification_count is rated Low

This tool performs a straightforward data retrieval operation. It queries the notification system to return a count, which is a read-only operation with no side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is minimal—an agent could only retrieve notification counts, which poses no security risk.

From the tool's definition Tool name 'get_unread_notification_count' and description 'Get the count of unread notifications' indicate a query operation that retrieves data without modification.

The rule that runs get_unread_notification_count safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_unread_notification_count, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_unread_notification_count": {}
  }
}

Questions about get_unread_notification_count