list_notifications

List inbox notifications. Returns notifications sorted by modification date (newest first). Supports filtering by read/archived status.

SERVERHuly SOURCEdugynoo/huly-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/list-notifications.md

WHAT IT DOES

What list_notifications does on Huly

AI agents call list_notifications 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.

RISK

Why list_notifications is rated Low

The tool performs data retrieval only ('list', 'returns', 'filtering') with no capability to create, modify, delete, or execute operations. It is a straightforward query operation on existing notification records, making it a Read category risk with low severity — an AI agent misusing it could only access existing notifications without causing harm.

From the tool's definition Tool description states 'List inbox notifications' with filtering by read/archived status. This is a read-only operation that retrieves and queries notification data without modifying or triggering any side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs list_notifications 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 list_notifications, this is the rule to start with:

list_notifications Allowed

list_notifications is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_notifications call is checked against it from then on.

FAQ

Questions about list_notifications

What does the list_notifications tool do? +

List inbox notifications. Returns notifications sorted by modification date (newest first). Supports filtering by read/archived status. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_notifications? +

Register the Huly MCP server in PolicyLayer and add a rule for list_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 Huly. Nothing to install.

What risk level is list_notifications? +

list_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_notifications? +

Yes. Add a rate_limit block to the list_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.

How do I block list_notifications completely? +

Set action: deny in the PolicyLayer policy for list_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.

What MCP server provides list_notifications? +

list_notifications is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →