archive_notification
Archive a notification. Archived notifications are hidden from the main inbox view.
This record as markdown: /tools/dugynoo-huly-mcp/archive-notification.md
What archive_notification does on Huly
AI agents use archive_notification 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 is rated Medium
Archiving a notification is a reversible write operation that modifies the notification's state/metadata (visibility) but does not delete, execute code, or cause financial impact. The user can unarchive notifications if needed. This falls squarely in the Write category with low severity since it only affects notification presentation in the inbox with minimal blast radius.
From the tool's definition Tool name 'archive_notification' and description 'Archive a notification. Archived notifications are hidden from the main inbox view.' indicates a state modification operation that changes notification visibility without deleting or destroying data.
Attacks that exploit this kind of access
The rule that runs archive_notification 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, this is the rule to start with:
archive_notification 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 call is checked against it from then on.
Questions about archive_notification
Archive a notification. Archived notifications are hidden from the main inbox view. 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: 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 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 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. 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 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