mark_notification_read
Mark a notification as read (deletes it)
This record as markdown: /tools/aiquila-nextcloud-mcp-server/mark-notification-read.md
What mark_notification_read does on AIquila — Nextcloud MCP Server
AI agents use mark_notification_read to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | number | Yes | The notification ID to mark as read |
Parameters from the server's own tool schema.
Why mark_notification_read is rated Medium
While the tool deletes a notification, this is a routine, reversible operation typical of notification management systems (notifications can typically be recovered from logs or recreated). This is not Destructive in the irreversible sense of data loss, but rather Write since it modifies application state (marks as read/removes from active notifications).
From the tool's definition Tool description states 'Mark a notification as read (deletes it)' - the parenthetical indicates deletion behavior, which modifies state by removing the notification from the unread set.
Attacks that exploit this kind of access
The rule that runs mark_notification_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_notification_read, this is the rule to start with:
mark_notification_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 AIquila — Nextcloud MCP Server, apply this rule, and every mark_notification_read call is checked against it from then on.
Questions about mark_notification_read
Mark a notification as read (deletes it). It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
mark_notification_read accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for mark_notification_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 AIquila — Nextcloud MCP Server. Nothing to install.
mark_notification_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_notification_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_notification_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_notification_read is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue