archive_notification_context
Archive all inbox notifications in a notification context. Idempotent: returns count 0 when no active notifications remain.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/archive-notification-context.md
What archive_notification_context does on Huly
AI agents use archive_notification_context 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_notification_context is rated Medium
Archiving notifications is a reversible write operation that changes notification state without permanently destroying data. While it affects user information organization, the action can be undone by un-archiving. This is less severe than Destructive (which would be irreversible deletion) but more impactful than a simple Read operation.
From the tool's definition Tool performs 'archive' action on notifications, which modifies their state (marking them as archived) rather than permanently deleting them. Description states it is 'idempotent' and returns a count, indicating a reversible state change.
Attacks that exploit this kind of access
The rule that runs archive_notification_context 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_notification_context, this is the rule to start with:
archive_notification_context 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_notification_context call is checked against it from then on.
Questions about archive_notification_context
Archive all inbox notifications in a notification context. Idempotent: returns count 0 when no active notifications remain. 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_notification_context: 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_notification_context 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_notification_context 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_notification_context. 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_notification_context 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