mark_notification_thread_read

Mark a notification thread as read (or another status) by ID

SERVERForgejo SOURCEsqcows/forgejo-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/sqcows-forgejo-mcp/mark-notification-thread-read.md

WHAT IT DOES

What mark_notification_thread_read does on Forgejo

AI agents use mark_notification_thread_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.

RISK

Why mark_notification_thread_read is rated Medium

Updates notification state without creating data or irreversible changes.

From the tool's definition Mark notification thread as read; modifies notification status reversibly.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mark_notification_thread_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_notification_thread_read, this is the rule to start with:

mark_notification_thread_read Rate-limited

mark_notification_thread_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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_notification_thread_read": {
      "limits": [
        {
          "counter": "mark_notification_thread_read_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Forgejo, apply this rule, and every mark_notification_thread_read call is checked against it from then on.

FAQ

Questions about mark_notification_thread_read

What does the mark_notification_thread_read tool do? +

Mark a notification thread as read (or another status) by ID. 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.

How do I enforce a policy on mark_notification_thread_read? +

Register the Forgejo MCP server in PolicyLayer and add a rule for mark_notification_thread_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.

What risk level is mark_notification_thread_read? +

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

Can I rate-limit mark_notification_thread_read? +

Yes. Add a rate_limit block to the mark_notification_thread_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_notification_thread_read completely? +

Set action: deny in the PolicyLayer policy for mark_notification_thread_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_notification_thread_read? +

mark_notification_thread_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.

KEEP EXPLORING

More on Forgejo, and thousands of servers like it.

This server

All 457 Forgejo tools →

Across the catalogue

sms_mark_read on Twilio SMS MCP Server →mark-as-read on Meme MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →