manage_repository_notification_subscription

Manage a repository notification subscription: ignore, watch, or delete repository notifications subscription for the provided repository.

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

Medium RISK CLASS

Category Write

Parameters 30 required

Recommended Rate-limitedsee the rule below

Registry record Grade D, identity verified Pull the record →

This record as markdown: /tools/github/manage-repository-notification-subscription.md

WHAT IT DOES

What manage_repository_notification_subscription does on GitHub

AI agents use manage_repository_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
`repo`	string	—	The name of the repository.
`owner`	string	—	The account owner of the repository.
`action`	string	—	Action to perform: ignore, watch, or delete the repository notification subscription.

Parameters from the server's own tool schema.

RISK

Why manage_repository_notification_subscription is rated Medium

This tool modifies user notification preferences and subscription settings for a repository. While 'delete subscription' is present, it refers to deleting a notification subscription (reversible preference change), not deleting repository data. The operations are side-effecting but reversible: subscriptions can be re-enabled or reconfigured.

From the tool's definition Tool description states 'Manage a repository notification subscription: ignore, watch, or delete repository notifications subscription' — the operations (ignore, watch, delete) modify subscription state but are reversible.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

manage_repository_notification_subscription Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "manage_repository_notification_subscription": {
      "limits": [
        {
          "counter": "manage_repository_notification_subscription_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 manage_repository_notification_subscription call is checked against it from then on.

FAQ

Questions about manage_repository_notification_subscription

What does the manage_repository_notification_subscription tool do? +

Manage a repository notification subscription: ignore, watch, or delete repository notifications subscription for the provided repository. 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.

What parameters does manage_repository_notification_subscription accept? +

manage_repository_notification_subscription accepts 3 parameters: repo, owner, action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on manage_repository_notification_subscription? +

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

What risk level is manage_repository_notification_subscription? +

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

Can I rate-limit manage_repository_notification_subscription? +

Yes. Add a rate_limit block to the manage_repository_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.

How do I block manage_repository_notification_subscription completely? +

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

What MCP server provides manage_repository_notification_subscription? +

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

KEEP EXPLORING

More on GitHub, and thousands of servers like it.

This server

All 86 GitHub tools →

Across the catalogue

aiva_subscription_actions on AIVA MCP Server → The MCP Attack Database →

Guides

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