update_notification_type_setting
Enable or disable one notification type for one provider. Validates both IDs against authoritative model definitions when available, and creates a type setting only when the provider is configurable. Compatible REST fallback is preserved and explicitly warned.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/update-notification-type-setting.md
What update_notification_type_setting does on Huly
AI agents use update_notification_type_setting to create or update resources in Huly, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Huly environment.
Why update_notification_type_setting is rated Medium
This tool modifies notification settings (a Write operation) rather than reading, executing arbitrary code, destroying data, or moving money. The severity is medium because misuse could spam or silence notifications affecting user experience and communication, but changes are reversible. Confidence is 0.85 because the description is clear on intent but doesn't explicitly detail the scope of potential side effects.
From the tool's definition Tool description states 'Enable or disable one notification type for one provider' and 'creates a type setting' — these are reversible modifications that change notification preferences without destroying data.
Attacks that exploit this kind of access
The rule that runs update_notification_type_setting 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 update_notification_type_setting, this is the rule to start with:
update_notification_type_setting stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 update_notification_type_setting call is checked against it from then on.
Questions about update_notification_type_setting
Enable or disable one notification type for one provider. Validates both IDs against authoritative model definitions when available, and creates a type setting only when the provider is configurable. Compatible REST fallback is preserved and explicitly warned. It is categorised as a Write tool in the Huly MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Huly MCP server in PolicyLayer and add a rule for update_notification_type_setting: 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.
update_notification_type_setting is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_notification_type_setting 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 update_notification_type_setting. 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.
update_notification_type_setting 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