delete-thread-subscription

THE RISK

Critical Risk

Why delete-thread-subscription needs a policy

Deleting a thread subscription is an irreversible removal action — once unsubscribed, the subscription is gone and future notifications for that thread will not be received unless explicitly re-subscribed. The 'delete' prefix and 'unsubscribe' action indicate removal of a persistent resource.

From the tool's definition 'delete-thread-subscription' and 'Unsubscribe from a GitHub notification thread'

Documented attack patterns abuse exactly the kind of access delete-thread-subscription gives an agent:

POLICY

How to control delete-thread-subscription

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 delete-thread-subscription:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete-thread-subscription"
  ]
}

delete-thread-subscription disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register GitHub Notifications MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitHub Notifications MCP Server 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 Read get-thread Get information about a GitHub notification thread Read get-thread-subscription Get subscription status for a GitHub notification thread

All 11 GitHub Notifications MCP Server tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in GitHub Notifications MCP Server → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about delete-thread-subscription

What does the delete-thread-subscription tool do? +

Unsubscribe from a GitHub notification thread. It is categorised as a Destructive tool in the GitHub Notifications MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete-thread-subscription? +

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

What risk level is delete-thread-subscription? +

delete-thread-subscription is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete-thread-subscription? +

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

Set action: deny in the PolicyLayer policy for delete-thread-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 delete-thread-subscription? +

delete-thread-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.

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 →