update_notification_provider_setting
Update notification provider setting. Enable or disable notifications for a specific provider.
This record as markdown: /tools/dugynoo-huly-mcp/update-notification-provider-setting.md
What update_notification_provider_setting does on Huly
AI agents use update_notification_provider_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_provider_setting is rated Medium
This tool creates or modifies data reversibly by updating notification settings. While the changes affect notification delivery, they are not destructive (can be undone by updating again), not financial, not code execution, and not read-only. The severity is medium because misconfiguration could disable important notifications, disrupting workflows, but the effect is limited in scope and reversible.
From the tool's definition The tool name 'update_notification_provider_setting' and description 'Update notification provider setting. Enable or disable notifications for a specific provider' directly indicate modification of configuration data.
Attacks that exploit this kind of access
The rule that runs update_notification_provider_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_provider_setting, this is the rule to start with:
update_notification_provider_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_provider_setting call is checked against it from then on.
Questions about update_notification_provider_setting
Update notification provider setting. Enable or disable notifications for a specific provider. 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_provider_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_provider_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_provider_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_provider_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_provider_setting 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.
More on Huly, and thousands of servers like it.
This server
Across the catalogue