list_notification_providers
List model-declared notification providers such as inbox, push, and sound. Use returned provider IDs for setting updates. Older REST servers may return compatibility metadata with an explicit tool warning.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/list-notification-providers.md
What list_notification_providers does on Huly
AI agents call list_notification_providers 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 list_notification_providers is rated Low
This tool queries and returns information about available notification providers without creating, modifying, deleting, or executing any operations. It is purely informational and read-only in nature. The low severity reflects minimal blast radius if misused by an agent—it only exposes configuration metadata about notification systems.
From the tool's definition Tool name 'list_notification_providers' and description states 'List model-declared notification providers' — a retrieval operation with no side effects. Returns provider IDs and metadata for informational purposes only.
Attacks that exploit this kind of access
The rule that runs list_notification_providers 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_notification_providers, this is the rule to start with:
list_notification_providers is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every list_notification_providers call is checked against it from then on.
Questions about list_notification_providers
List model-declared notification providers such as inbox, push, and sound. Use returned provider IDs for setting updates. Older REST servers may return compatibility metadata with an explicit tool warning. It is categorised as a Read tool in the Huly MCP Server, which means it retrieves data without modifying state.
Register the Huly MCP server in PolicyLayer and add a rule for list_notification_providers: 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.
list_notification_providers 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 list_notification_providers 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 list_notification_providers. 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.
list_notification_providers is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
This server
Across the catalogue