list_notification_types
List model-declared notification types. Use returned type IDs for provider-specific 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-types.md
What list_notification_types does on Huly
AI agents call list_notification_types 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_types is rated Low
This tool retrieves notification type configuration data from the Huly system. It performs a query operation that returns type identifiers and possibly compatibility metadata, with no modification, deletion, or execution of external operations. No financial impact or destructive capability is present. This is a straightforward data retrieval operation.
From the tool's definition Tool description states 'List model-declared notification types' and 'Use returned type IDs for provider-specific setting updates'. The verb 'list' and the read-only nature of querying notification type metadata indicates retrieval without side effects.
Attacks that exploit this kind of access
The rule that runs list_notification_types 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_types, this is the rule to start with:
list_notification_types 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_types call is checked against it from then on.
Questions about list_notification_types
List model-declared notification types. Use returned type IDs for provider-specific 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_types: 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_types 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_types 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_types. 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_types 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