github_set_topics

Replace the topic tags on a repo (used for GitHub search ranking).

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-set-topics.md

WHAT IT DOES

What github_set_topics does on Github

AI agents use github_set_topics 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_set_topics is rated Medium

This tool modifies repository metadata (topic tags) in a reversible manner—new topics can be set again, and the change does not delete data or cause irreversible effects. While it could impact a repository's visibility if misused by an AI agent (e.g., removing all topics to hide a repo from search), the operation itself is non-destructive and reversible, placing it in the Write category rather than Destructive.

From the tool's definition Tool description states it 'Replace[s] the topic tags on a repo', which is a modification operation. Topics are metadata on repositories that affect GitHub search visibility and discoverability.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

github_set_topics Rate-limited

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

FAQ

Questions about github_set_topics

What does the github_set_topics tool do? +

Replace the topic tags on a repo (used for GitHub search ranking). 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_set_topics? +

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

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

Can I rate-limit github_set_topics? +

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

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

github_set_topics 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

set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP →qt_set_property on Qt → The MCP Attack Database →

Guides

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