mark_notifications_read
Mark all notifications as read for the authenticated user
This record as markdown: /tools/sqcows-forgejo-mcp/mark-notifications-read.md
What mark_notifications_read does on Forgejo
AI agents use mark_notifications_read to create or update resources in Forgejo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Forgejo environment.
Why mark_notifications_read is rated Medium
This tool modifies notification state (read status) for the authenticated user, which is a reversible write operation. It does not execute arbitrary code, delete data permanently, or move money. While it changes state in the system, the scope is limited to the user's own notification preferences and the change is easily reversible (notifications can be marked unread again).
From the tool's definition Tool name 'mark_notifications_read' and description 'Mark all notifications as read for the authenticated user' indicate a state change operation that modifies notification records.
Attacks that exploit this kind of access
The rule that runs mark_notifications_read safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Forgejo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_notifications_read, this is the rule to start with:
mark_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 Forgejo, apply this rule, and every mark_notifications_read call is checked against it from then on.
Questions about mark_notifications_read
Mark all notifications as read for the authenticated user. It is categorised as a Write tool in the Forgejo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Forgejo MCP server in PolicyLayer and add a rule for mark_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 Forgejo. Nothing to install.
mark_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_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_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_notifications_read is provided by the Forgejo MCP server (sqcows/forgejo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Forgejo, and thousands of servers like it.
This server
Across the catalogue