gh_release_create · GitHub CLI MCP Server MCP: Risk & Policy

WHAT IT DOES

What gh_release_create does on GitHub CLI MCP Server

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

WHY IT NEEDS A POLICY

Why gh_release_create needs a policy

This tool creates a new release, which is a reversible write operation. While releases can be deleted, the primary action is creation/modification of repository metadata and artifacts. This is more severe than a simple Read operation but less severe than Destructive (which would be permanent deletion) or Execute (which would run arbitrary code).

From the tool's definition Tool name 'gh_release_create' and description 'Create a new release' indicate creation of a new release artifact in a GitHub repository.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

gh_release_create Rate-limited

gh_release_create 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": {
    "gh_release_create": {
      "limits": [
        {
          "counter": "gh_release_create_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitHub CLI MCP Server, so you can run agents against it safely.

FAQ

Questions about gh_release_create

What does the gh_release_create tool do? +

Create a new release. It is categorised as a Write tool in the GitHub CLI 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 gh_release_create? +

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

What risk level is gh_release_create? +

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

Can I rate-limit gh_release_create? +

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

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

gh_release_create is provided by the GitHub CLI MCP Server MCP server (munch-group/gh-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.