github_unstar_repo

Unstar a repo.

SERVERGithub SOURCEdkeeno/github-mcp-server

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-unstar-repo.md

WHAT IT DOES

What github_unstar_repo does on Github

AI agents use github_unstar_repo 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.

RISK

Why github_unstar_repo is rated Medium

Unstarring a repository is a reversible write operation that modifies the user's GitHub profile state by removing a star. It does not create permanent artifacts, delete data, execute code, or have financial implications. The impact is limited to the user's own interaction metadata and is easily reversible by starring again. Severity is low due to minimal blast radius and reversibility.

From the tool's definition Tool name 'github_unstar_repo' and description 'Unstar a repo' indicate modification of user state (removing a star from a repository).

Attacks that exploit this kind of access

RECOMMENDED RULE

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

github_unstar_repo Rate-limited

github_unstar_repo 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": {
    "github_unstar_repo": {
      "limits": [
        {
          "counter": "github_unstar_repo_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 github_unstar_repo call is checked against it from then on.

FAQ

Questions about github_unstar_repo

What does the github_unstar_repo tool do? +

Unstar a repo. 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.

How do I enforce a policy on github_unstar_repo? +

Register the Github MCP server in PolicyLayer and add a rule for github_unstar_repo: 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 github_unstar_repo? +

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

Can I rate-limit github_unstar_repo? +

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

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

github_unstar_repo is provided by the Github MCP server (dkeeno/github-mcp-server). 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 69 Github tools →

Across the catalogue

The MCP Attack Database →

Guides

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