manage_notification_subscription
Manage a notification subscription: ignore, watch, or delete a notification thread subscription.
This record as markdown: /tools/github/manage-notification-subscription.md
What manage_notification_subscription does on GitHub
AI agents use manage_notification_subscription 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | Action to perform: ignore, watch, or delete the notification subscription. |
notificationID | string | — | The ID of the notification thread. |
Parameters from the server's own tool schema.
Why manage_notification_subscription is rated Medium
This tool modifies notification preferences (subscription state), which is reversible user configuration rather than destructive data deletion or financial action. It is Write-category because it updates subscription settings. Severity is low because misuse would only affect notification filtering preferences—an inconvenience but not a security breach or data loss.
From the tool's definition Tool description states 'Manage a notification subscription: ignore, watch, or delete a notification thread subscription.' The operations are 'ignore', 'watch', or 'delete' applied to subscription state rather than core data.
Attacks that exploit this kind of access
The rule that runs manage_notification_subscription 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 manage_notification_subscription, this is the rule to start with:
manage_notification_subscription 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 GitHub, apply this rule, and every manage_notification_subscription call is checked against it from then on.
Questions about manage_notification_subscription
Manage a notification subscription: ignore, watch, or delete a notification thread subscription. 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.
manage_notification_subscription accepts 2 parameters: action, notificationID. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for manage_notification_subscription: 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.
manage_notification_subscription 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 manage_notification_subscription 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 manage_notification_subscription. 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.
manage_notification_subscription 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.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue