mark_notification_unread
Mark a notification as unread. Idempotent: returns success when the notification is already unread.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/mark-notification-unread.md
What mark_notification_unread does on Huly
AI agents use mark_notification_unread 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 mark_notification_unread is rated Medium
Marking a notification as unread is a state modification that changes data (notification status) but is fully reversible—the user or another agent can mark it read again. This is characteristic of Write operations. The impact is minimal (affects only notification status visibility), making severity low. High confidence due to clear, explicit description of the action performed.
From the tool's definition Tool description states 'Mark a notification as unread', which modifies the read/unread state of a notification object. This is a reversible state change (can be marked read again). Idempotent behavior confirms it does not have destructive side effects.
Attacks that exploit this kind of access
The rule that runs mark_notification_unread 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 mark_notification_unread, this is the rule to start with:
mark_notification_unread 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 mark_notification_unread call is checked against it from then on.
Questions about mark_notification_unread
Mark a notification as unread. Idempotent: returns success when the notification is already unread. 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 mark_notification_unread: 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.
mark_notification_unread 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 mark_notification_unread 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 mark_notification_unread. 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.
mark_notification_unread 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