get_release_by_tag

Get a release by tag name

SERVERGitHub SOURCEoci:ghcr.io/aifity/omnigit-mcp:0.5.0

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-aifity-omnigit-mcp/get-release-by-tag.md

WHAT IT DOES

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.

RISK

Why get_release_by_tag is rated Low

This tool retrieves metadata about a GitHub release identified by a tag. It performs a read-only query operation with no capability to modify, delete, or execute code. The blast radius of misuse is minimal—an agent could only access release information that would typically be public or already accessible to the authenticated user.

From the tool's definition Tool name 'get_release_by_tag' and description 'Get a release by tag name' indicate a retrieval operation with no side effects. This queries existing release data without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Allowed

get_release_by_tag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_release_by_tag": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about get_release_by_tag

What does the get_release_by_tag tool do? +

Get a release by tag name. It is categorised as a Read tool in the GitHub MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_release_by_tag? +

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.

What risk level is get_release_by_tag? +

get_release_by_tag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_release_by_tag? +

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.

How do I block get_release_by_tag completely? +

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.

What MCP server provides get_release_by_tag? +

get_release_by_tag is provided by the GitHub MCP server (oci:ghcr.io/aifity/omnigit-mcp:0.5.0). 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 245 GitHub tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →