github_get_release

Get details of a specific release

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/github-get-release.md

WHAT IT DOES

What github_get_release does on Sage MCP

AI agents call github_get_release to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_get_release is rated Low

This tool retrieves release metadata from GitHub (version numbers, descriptions, assets, timestamps, etc.). It performs no data mutation, execution, or destructive actions. The blast radius of misuse is minimal—an agent could only exfiltrate public or authorized release information, which is a read-level risk.

From the tool's definition Tool name 'github_get_release' and description 'Get details of a specific release' indicate a retrieval operation with no modification or side effects. The verb 'get' and noun 'details' confirm read-only semantics.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_get_release safely

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

github_get_release Allowed

github_get_release 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": {
    "github_get_release": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every github_get_release call is checked against it from then on.

FAQ

Questions about github_get_release

What does the github_get_release tool do? +

Get details of a specific release. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_get_release? +

Register the Sage MCP server in PolicyLayer and add a rule for github_get_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 Sage MCP. Nothing to install.

What risk level is github_get_release? +

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

Can I rate-limit github_get_release? +

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

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

github_get_release is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage 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 →