release-list

Lists GitHub releases for a repository. Returns structured list with tag, name, draft/prerelease/latest status, publish date, and creation date.

SERVERLint SOURCEDave-London/Pare

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-dave-london-lint/release-list.md

WHAT IT DOES

What release-list does on Lint

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

RISK

Why release-list is rated Low

This tool retrieves and returns structured information about GitHub releases without creating, modifying, deleting, executing code, or committing financial obligations. It is a straightforward query operation with no side effects. Severity is low because leaking release metadata poses minimal security risk and the tool has no capability to affect systems or data.

From the tool's definition Tool 'release-list' is described as 'Lists GitHub releases for a repository' with read-only retrieval of release metadata (tag, name, status, dates). Uses verb 'Lists' indicating data query without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs release-list safely

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

release-list Allowed

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

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

The button opens the PolicyLayer dashboard: create your workspace, connect Lint, apply this rule, and every release-list call is checked against it from then on.

FAQ

Questions about release-list

What does the release-list tool do? +

Lists GitHub releases for a repository. Returns structured list with tag, name, draft/prerelease/latest status, publish date, and creation date. It is categorised as a Read tool in the Lint MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on release-list? +

Register the Lint MCP server in PolicyLayer and add a rule for release-list: 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 Lint. Nothing to install.

What risk level is release-list? +

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

Can I rate-limit release-list? +

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

Set action: deny in the PolicyLayer policy for release-list. 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 release-list? +

release-list is provided by the Lint MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Lint, and thousands of servers like it.

This server

All 202 Lint tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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