github_repo_info

Get current repo info (stars, forks, language, license).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 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-repo-info.md

WHAT IT DOES

What github_repo_info does on Yaver

AI agents call github_repo_info 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.

RISK

Why github_repo_info is rated Low

This tool only retrieves and displays information about a repository's public metadata. It performs no modifications, deletions, executions, or financial operations. The action is a simple read/fetch of repository statistics and configuration details, which is the lowest-risk category.

From the tool's definition Tool description states 'Get current repo info (stars, forks, language, license)' — a pure query operation that retrieves publicly available metadata about a GitHub repository with no side effects.

Risk signalsAccepts file system path (directory)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

github_repo_info Allowed

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

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_repo_info call is checked against it from then on.

FAQ

Questions about github_repo_info

What does the github_repo_info tool do? +

Get current repo info (stars, forks, language, license). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does github_repo_info accept? +

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

How do I enforce a policy on github_repo_info? +

Register the Yaver MCP server in PolicyLayer and add a rule for github_repo_info: 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_repo_info? +

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

Can I rate-limit github_repo_info? +

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

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

github_repo_info 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

get_team_info on CTFtime MCP Server → The MCP Attack Database →

Guides

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