git_release

Automated release management with version tagging and changelog generation

SERVERGitHub MCP Server SOURCE0xshariq/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/0xshariq-github-mcp-server/git-release.md

WHAT IT DOES

What git_release does on GitHub MCP Server

AI agents use git_release to create or update resources in GitHub MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitHub MCP Server environment.

RISK

Why git_release is rated Medium

git_release creates (tags) and modifies (changelog) repository data. While version tagging is a standard git operation, it creates permanent markers in repository history and can affect downstream automation (CI/CD pipelines, package managers). The changelog generation modifies files. These are Write operations rather than Execute because they don't run arbitrary code—they follow a defined release process.

From the tool's definition Tool performs 'version tagging and changelog generation' which creates new git tags and modifies changelog files. These are reversible write operations that create structured data artifacts in the repository.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs git_release safely

PolicyLayer is an MCP gateway: it sits between your AI agents and GitHub MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For git_release, this is the rule to start with:

git_release Rate-limited

git_release 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": {
    "git_release": {
      "limits": [
        {
          "counter": "git_release_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 MCP Server, apply this rule, and every git_release call is checked against it from then on.

FAQ

Questions about git_release

What does the git_release tool do? +

Automated release management with version tagging and changelog generation. It is categorised as a Write tool in the GitHub MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on git_release? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for git_release: 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 MCP Server. Nothing to install.

What risk level is git_release? +

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

Can I rate-limit git_release? +

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

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

git_release is provided by the GitHub MCP Server MCP server (0xshariq/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 MCP Server, and thousands of servers like it.

This server

All 33 GitHub MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

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