get_release_by_tag
Get a specific release by its tag name in a GitHub repository
This record as markdown: /tools/github/get-release-by-tag.md
What get_release_by_tag does on GitHub
AI agents call get_release_by_tag to retrieve information from GitHub without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tag | string | — | Tag name (e.g., 'v1.0.0') |
repo | string | — | Repository name |
owner | string | — | Repository owner |
Parameters from the server's own tool schema.
Why get_release_by_tag is rated Low
This tool retrieves information about a specific release from a GitHub repository using a tag name as a query parameter. It performs a read-only operation that does not modify, execute, delete, or incur financial obligations. The blast radius of misuse is minimal—an agent could retrieve public or authorized release information, but cannot cause harm through data retrieval alone.
From the tool's definition Tool name 'get_release_by_tag' and description 'Get a specific release by its tag name in a GitHub repository' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs get_release_by_tag 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 get_release_by_tag, this is the rule to start with:
get_release_by_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect GitHub, apply this rule, and every get_release_by_tag call is checked against it from then on.
Questions about get_release_by_tag
Get a specific release by its tag name in a GitHub repository. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.
get_release_by_tag accepts 3 parameters: tag, repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the GitHub MCP server in PolicyLayer and add a rule for get_release_by_tag: 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.
get_release_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_release_by_tag 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.
Set action: deny in the PolicyLayer policy for get_release_by_tag. 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.
get_release_by_tag is provided by the GitHub MCP server (oci:ghcr.io/github/github-mcp-server:1.3.0). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on GitHub, and thousands of servers like it.
This server
Across the catalogue