create_release · GitHub MCP Server MCP: Risk & Policy

WHAT IT DOES

What create_release does on GitHub MCP Server

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

WHY IT NEEDS A POLICY

Why create_release needs a policy

GitHub releases are important software artifacts that tag specific commits and can be publicly distributed. Creating a release is reversible (releases can be deleted), so it falls under Write rather than Destructive. However, it carries medium severity because malicious releases could mislead users, distribute unauthorized code versions, or damage project reputation.

From the tool's definition Tool name 'create_release' indicates creation of a release object in a GitHub repository. Based on sibling tools (create_branch, create_issue, create_gist, create_or_update_file) which are Write operations, this tool follows the same pattern of creating new…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_release Rate-limited

create_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": {
    "create_release": {
      "limits": [
        {
          "counter": "create_release_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about create_release

What does the create_release tool do? +

create_release. 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 create_release? +

Register the GitHub MCP Server MCP server in PolicyLayer and add a rule for create_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 create_release? +

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

Can I rate-limit create_release? +

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

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

create_release is provided by the GitHub MCP Server MCP server (software-engineer-mj/github-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.