mark_item_unread
Mark a single news item as unread.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/mark-item-unread.md
What mark_item_unread does on AIquila — Nextcloud MCP Server
AI agents use mark_item_unread 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 |
|---|---|---|---|
itemId | number | Yes | The item ID |
Parameters from the server's own tool schema.
Why mark_item_unread is rated Medium
This tool changes metadata (read status) of a news/feed item reversibly. The user can re-mark it as read, making it a Write operation rather than Destructive. The blast radius is minimal—affecting only a single news item's read status with no data loss or external effects. Severity is low due to the trivial nature of the operation and its reversibility.
From the tool's definition Tool description states 'Mark a single news item as unread,' which modifies state of a news item (mark as unread) without deleting data or executing arbitrary operations.
Attacks that exploit this kind of access
The rule that runs mark_item_unread 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_item_unread, this is the rule to start with:
mark_item_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 AIquila — Nextcloud MCP Server, apply this rule, and every mark_item_unread call is checked against it from then on.
Questions about mark_item_unread
Mark a single news item as unread. 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_item_unread accepts 1 parameter: itemId. Required: itemId. 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_item_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 AIquila — Nextcloud MCP Server. Nothing to install.
mark_item_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_item_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_item_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_item_unread 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