unarchive_notification
Unarchive a notification so it can appear in active notification lists again. Idempotent when already active.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/unarchive-notification.md
What unarchive_notification does on Huly
AI agents use unarchive_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 unarchive_notification is rated Medium
This tool modifies the state of a notification by changing its archive status, qualifying it as a Write operation. It is reversible (the notification can be re-archived), causes no data destruction, executes no external code, and involves no financial impact. The low severity reflects the minimal blast radius—affecting only UI visibility of notifications without altering core data or triggering external operations.
From the tool's definition Tool name 'unarchive_notification' and description 'Unarchive a notification so it can appear in active notification lists again' indicate a state modification operation that reverses a prior archive action.
Attacks that exploit this kind of access
The rule that runs unarchive_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 unarchive_notification, this is the rule to start with:
unarchive_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 unarchive_notification call is checked against it from then on.
Questions about unarchive_notification
Unarchive a notification so it can appear in active notification lists again. Idempotent when already active. 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 unarchive_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.
unarchive_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 unarchive_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 unarchive_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.
unarchive_notification 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