mark_all_notifications_read
Mark all unread notifications as read. Returns the count of notifications marked.
This record as markdown: /tools/dugynoo-huly-mcp/mark-all-notifications-read.md
What mark_all_notifications_read does on Huly
AI agents use mark_all_notifications_read 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_all_notifications_read is rated Medium
This tool changes notification status from unread to read, which is a reversible modification (Write category). The change is not destructive as notifications remain intact. Severity is low because marking notifications as read has minimal blast radius — it only affects UI state and notification display for the user, with no impact on core data, financial operations, or system integrity.
From the tool's definition Tool performs 'Mark all unread notifications as read' — modifies notification state without deletion. Returns count of notifications marked, indicating a state-change operation.
Attacks that exploit this kind of access
The rule that runs mark_all_notifications_read 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_all_notifications_read, this is the rule to start with:
mark_all_notifications_read 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_all_notifications_read call is checked against it from then on.
Questions about mark_all_notifications_read
Mark all unread notifications as read. Returns the count of notifications marked. 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_all_notifications_read: 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_all_notifications_read 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_all_notifications_read 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_all_notifications_read. 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_all_notifications_read 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