// MCP TOOL REFERENCE

GITHUB NOTIFICATIONS MCP SERVER TOOLS

11 tools from the GitHub Notifications MCP Server MCP Server, categorised by risk level.

View the GitHub Notifications MCP Server policy →
// ALL 11 GITHUB NOTIFICATIONS MCP SERVER TOOLS
READ 4 tools
Read get-thread Get information about a GitHub notification thread Read get-thread-subscription Get subscription status for a GitHub notification thread Read list-notifications List GitHub notifications for the authenticated user Read list-repo-notifications List GitHub notifications for a specific repository
WRITE 6 tools
Write manage-repo-subscription Manage repository subscription settings including fine-grained notification preferences Write mark-notifications-read Mark GitHub notifications as read Write mark-repo-notifications-read Mark GitHub notifications for a specific repository as read Write mark-thread-done Mark a GitHub notification thread as done Write mark-thread-read Mark a GitHub notification thread as read Write set-thread-subscription Subscribe to a GitHub notification thread
DESTRUCTIVE 1 tools
Destructive delete-thread-subscription Unsubscribe from a GitHub notification thread

Route GitHub Notifications MCP Server through PolicyLayer and every one of its 11 tools is checked against your policy before it runs.

CHECK YOUR STACK →

See every tool, the dangerous ones, and the token cost across your stack.

// FAQ
How many tools does the GitHub Notifications MCP Server MCP server have? +

The GitHub Notifications MCP Server MCP server exposes 11 tools across 3 categories: Read, Write, Destructive.

How do I enforce policies on GitHub Notifications MCP Server tools? +

Route the GitHub Notifications MCP Server server through the PolicyLayer gateway. Define allow, deny, or approval rules per tool in the dashboard; they are enforced on every call before it reaches the server.

What risk categories do GitHub Notifications MCP Server tools fall into? +

GitHub Notifications MCP Server tools are categorised as Read (4), Write (6), Destructive (1). Each category has a recommended default policy.

Enforce policy on every GitHub Notifications MCP Server tool call.

Start from GitHub Notifications MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

43,000+ MCP servers and 220,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.