mark_all_notifications_read

Mark all notifications as read

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

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/io-github-aifity-omnigit-mcp/mark-all-notifications-read.md

WHAT IT DOES

What mark_all_notifications_read does on GitHub

AI agents use mark_all_notifications_read to create or update resources in GitHub, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub environment.

RISK

Why mark_all_notifications_read is rated Medium

This tool modifies data (notification read status) in a reversible manner—the user can unread notifications again or the state can be reverted. It is not destructive (no deletion), not financial, and not code execution. The blast radius is minimal since it only affects notification metadata for the authenticated user, with no impact on actual repository data, code, or resources.

From the tool's definition Tool name 'mark_all_notifications_read' and description 'Mark all notifications as read' indicate a state change operation that modifies notification records by setting their read status.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mark_all_notifications_read safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mark_all_notifications_read, this is the rule to start with:

mark_all_notifications_read Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mark_all_notifications_read": {
      "limits": [
        {
          "counter": "mark_all_notifications_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 GitHub, apply this rule, and every mark_all_notifications_read call is checked against it from then on.

FAQ

Questions about mark_all_notifications_read

What does the mark_all_notifications_read tool do? +

Mark all notifications as read. It is categorised as a Write tool in the GitHub 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 GitHub 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 GitHub. 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 GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 245 GitHub 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 →