github_repo_releases

List a repository's releases. Returns a page of a repository's releases (momentum/health signal).

SERVERCrawlora SOURCEcrawlora-mcp

Low RISK CLASS

Category Read

Parameters 42 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/github-repo-releases.md

WHAT IT DOES

What github_repo_releases does on Crawlora

AI agents call github_repo_releases to retrieve information from Crawlora 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
`page`	integer	—	Page number
`repo`	string	Yes	Repository name
`owner`	string	Yes	Repository owner (user or org login)
`per_page`	integer	—	Results per page (max 100)

Parameters from the server's own tool schema.

RISK

Why github_repo_releases is rated Low

Even though github_repo_releases only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_repo_releases safely

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

github_repo_releases Allowed

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

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

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

FAQ

Questions about github_repo_releases

What does the github_repo_releases tool do? +

List a repository's releases. Returns a page of a repository's releases (momentum/health signal). It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.

What parameters does github_repo_releases accept? +

github_repo_releases accepts 4 parameters: page, repo, owner, per_page. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on github_repo_releases? +

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

What risk level is github_repo_releases? +

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

Can I rate-limit github_repo_releases? +

Yes. Add a rate_limit block to the github_repo_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.

How do I block github_repo_releases completely? +

Set action: deny in the PolicyLayer policy for github_repo_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.

What MCP server provides github_repo_releases? +

github_repo_releases is provided by the Crawlora MCP server (crawlora-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

The MCP Attack Database →

Guides

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