Manage repository subscription settings including fine-grained notification preferences
AI agents use manage-repo-subscription to create or update resources in GitHub Notifications MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub Notifications MCP Server environment.
This tool modifies notification subscription settings for a repository, which is a reversible configuration change (Write category). It does not delete data (not Destructive), execute external code (not Execute), or involve financial transactions (not Financial). Severity is medium because misconfiguration could flood or silence notifications, affecting workflow but remaining reversible.
From the tool's definition Tool name 'manage-repo-subscription' and description 'Manage repository subscription settings including fine-grained notification preferences' indicate modification of user notification preferences and subscription state.
Documented attack patterns abuse exactly the kind of access manage-repo-subscription gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GitHub Notifications MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for manage-repo-subscription:
{
"version": "1",
"default": "deny",
"tools": {
"manage-repo-subscription": {
"limits": [
{
"counter": "manage-repo-subscription_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}manage-repo-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.
Free to start. No card required.
Manage repository subscription settings including fine-grained notification preferences. It is categorised as a Write tool in the GitHub Notifications MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the GitHub Notifications MCP Server MCP server in PolicyLayer and add a rule for manage-repo-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 Notifications MCP Server. Nothing to install.
manage-repo-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-repo-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-repo-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-repo-subscription is provided by the GitHub Notifications MCP Server MCP server (mcollina/mcp-github-notifications). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
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.
Free to start. No card required.
11 GitHub Notifications MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.