This record as markdown: /tools/io-github-kivanccakmak-yaver/github-releases.md
What github_releases does on Yaver
AI agents call github_releases to retrieve information from Yaver 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 |
|---|---|---|---|
directory | string | — |
Parameters from the server's own tool schema.
Why github_releases is rated Low
This tool queries and returns GitHub release information without creating, modifying, deleting, or executing any operations. It is a straightforward read-only information retrieval function with minimal risk. Even if an AI agent misuses it, the worst outcome is retrieving unintended release data, which has negligible security impact.
From the tool's definition Tool name 'github_releases' and description 'List GitHub releases' indicate a retrieval operation with no modification capability.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs github_releases safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_releases, this is the rule to start with:
github_releases 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 Yaver, apply this rule, and every github_releases call is checked against it from then on.
Questions about github_releases
List GitHub releases. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
github_releases accepts 1 parameter: directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for github_releases: 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 Yaver. Nothing to install.
github_releases 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 github_releases 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 github_releases. 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.
github_releases is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Yaver, and thousands of servers like it.
This server
Across the catalogue