github_repo
Public GitHub repository stats: description, stars, forks, open issues, primary language, license, last push date, and archived status. Useful for assessing the health and maintenance of an open-source dependency. Keyless (60 req/hr unauthenticated).
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/github-repo.md
What github_repo does on Livedatalink
AI agents call github_repo to retrieve information from Livedatalink 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 | Repository as 'owner/repo', e.g. 'facebook/react'. |
Parameters from the server's own tool schema.
Why github_repo is rated Low
The tool only queries and returns read-only information about publicly available GitHub repositories. It has no side effects, cannot modify data, and poses minimal risk if misused by an AI agent. The keyless, rate-limited (60 req/hr) design further indicates it is a safe read-only data source.
From the tool's definition Retrieves public repository metadata: 'description, stars, forks, open issues, primary language, license, last push date, and archived status'. No modification or deletion mentioned.
Attacks that exploit this kind of access
The rule that runs github_repo safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For github_repo, this is the rule to start with:
github_repo 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 Livedatalink, apply this rule, and every github_repo call is checked against it from then on.
Questions about github_repo
Public GitHub repository stats: description, stars, forks, open issues, primary language, license, last push date, and archived status. Useful for assessing the health and maintenance of an open-source dependency. Keyless (60 req/hr unauthenticated). It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
github_repo accepts 1 parameter: repo. Required: repo. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for github_repo: 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 Livedatalink. Nothing to install.
github_repo 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_repo 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_repo. 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_repo is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue