archive_all_notifications
Archive all notifications. Returns the count of notifications archived.
This record as markdown: /tools/dugynoo-huly-mcp/archive-all-notifications.md
What archive_all_notifications does on Huly
AI agents use archive_all_notifications 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 archive_all_notifications is rated Medium
Archiving is a state-modifying action that changes data (notifications from active to archived status) but remains reversible—archived notifications can typically be unarchived. This fits the Write category definition of actions that 'create or modify data reversibly'.
From the tool's definition The tool is named 'archive_all_notifications' and the description states it 'Archive all notifications. Returns the count of notifications archived.' This action modifies the state of notifications (marking them as archived) without permanently deleting them,…
Attacks that exploit this kind of access
The rule that runs archive_all_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 archive_all_notifications, this is the rule to start with:
archive_all_notifications 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 archive_all_notifications call is checked against it from then on.
Questions about archive_all_notifications
Archive all notifications. Returns the count of notifications archived. 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 archive_all_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.
archive_all_notifications 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 archive_all_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.
Set action: deny in the PolicyLayer policy for archive_all_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.
archive_all_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.
More on Huly, and thousands of servers like it.
This server
Across the catalogue