mark_all_notifications_read

Mark all unread notifications as read. Returns the count of notifications marked.

SERVERHuly SOURCEdugynoo/huly-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

Questions about mark_all_notifications_read

What does the mark_all_notifications_read tool do? +

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.

How do I enforce a policy on mark_all_notifications_read? +

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.

What risk level is mark_all_notifications_read? +

mark_all_notifications_read is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit mark_all_notifications_read? +

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.

How do I block mark_all_notifications_read completely? +

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.

What MCP server provides mark_all_notifications_read? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Huly's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.