github_stars

Get star count for any repo.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/github-stars.md

WHAT IT DOES

What github_stars does on Yaver

AI agents call github_stars 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
`repo`	string	Yes	owner/repo

Parameters from the server's own tool schema.

RISK

Why github_stars is rated Low

This tool retrieves public repository statistics (star count) from GitHub. It performs a read-only query with no side effects, data modification, code execution, or financial impact. The operation is informational only and returns existing public data.

From the tool's definition Tool name 'github_stars' and description 'Get star count for any repo' indicate a retrieval operation that queries GitHub metadata without modifying any data.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_stars 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_stars, this is the rule to start with:

github_stars Allowed

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

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

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

FAQ

Questions about github_stars

What does the github_stars tool do? +

Get star count for any repo. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does github_stars accept? +

github_stars accepts 1 parameter: repo. Required: repo. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on github_stars? +

Register the Yaver MCP server in PolicyLayer and add a rule for github_stars: 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.

What risk level is github_stars? +

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

Can I rate-limit github_stars? +

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

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

github_stars 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 645 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

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