github_repo_forks
List a repository's public forks. Returns a page of a repository's public forks (adopter signal).
This record as markdown: /tools/crawlora-mcp/github-repo-forks.md
What github_repo_forks does on Crawlora
AI agents call github_repo_forks 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 |
sort | string | — | Sort order |
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.
Why github_repo_forks is rated Low
This tool queries publicly available fork information about a GitHub repository. It performs a read-only operation (list) with no capability to modify data, execute code, or cause irreversible changes. The data retrieved is already public, so exposure carries minimal risk.
From the tool's definition Tool name and description: 'List a repository's public forks' — explicitly a retrieval/listing operation. Returns public data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs github_repo_forks 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_forks, this is the rule to start with:
github_repo_forks 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 Crawlora, apply this rule, and every github_repo_forks call is checked against it from then on.
Questions about github_repo_forks
List a repository's public forks. Returns a page of a repository's public forks (adopter signal). It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_repo_forks accepts 5 parameters: page, repo, sort, owner, per_page. Required: repo, owner. The full parameter table on this page comes from the server's own tool schema.
Register the Crawlora MCP server in PolicyLayer and add a rule for github_repo_forks: 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.
github_repo_forks 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_forks 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_forks. 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_forks 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.
More on Crawlora, and thousands of servers like it.
This server
Across the catalogue