list_notifications

SERVERGitHub SOURCEoci:ghcr.io/github/github-mcp-server:1.3.0

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/list-notifications.md

WHAT IT DOES

What list_notifications does on GitHub

AI agents call list_notifications to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`page`	number	—	Page number for pagination (min 1)
`repo`	string	—	Optional repository name. If provided with owner, only notifications for this repository are listed.
`owner`	string	—	Optional repository owner. If provided with repo, only notifications for this repository are listed.
`since`	string	—	Only show notifications updated after the given time (ISO 8601 format)
`before`	string	—	Only show notifications updated before the given time (ISO 8601 format)
`filter`	string	—	Filter notifications to, use default unless specified. Read notifications are ones that have already been acknowledged by the user. Participating notifications
`perPage`	number	—	Results per page for pagination (min 1, max 100)

Parameters from the server's own tool schema.

RISK

Why list_notifications is rated Low

This tool queries and retrieves existing notification data for the authenticated user without creating, modifying, deleting, or executing any operations. It is purely informational and produces no side effects, making it a Read category tool with low severity. The blast radius is minimal—misuse would only expose information the user already has access to.

From the tool's definition Tool description states it 'Lists all GitHub notifications' and 'retrieves' unread notifications, mentions, review requests, assignments, and updates.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

list_notifications Allowed

list_notifications is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_notifications": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about list_notifications

What does the list_notifications tool do? +

Lists all GitHub notifications for the authenticated user, including unread notifications, mentions, review requests, assignments, and updates on issues or pull requests. Use this tool whenever the user asks what to work on next, requests a summary of their GitHub activity, wants to see pending reviews, or needs to check for new updates or tasks. This tool is the primary way to discover actionable items, reminders, and outstanding work on GitHub. Always call this tool when asked what to work on next, what is pending, or what needs attention in GitHub. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

What parameters does list_notifications accept? +

list_notifications accepts 7 parameters: page, repo, owner, since, before, filter, perPage. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_notifications? +

Register the GitHub MCP server in PolicyLayer and add a rule for list_notifications: 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 list_notifications? +

list_notifications is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_notifications? +

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

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

list_notifications is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.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 86 GitHub tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →