github_user_followers
List a GitHub user's followers. Returns a page of the public accounts following a GitHub user.
This record as markdown: /tools/crawlora-mcp/github-user-followers.md
What github_user_followers does on Crawlora
AI agents call github_user_followers 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 |
per_page | integer | — | Results per page (max 100) |
username | string | Yes | GitHub username |
Parameters from the server's own tool schema.
Why github_user_followers is rated Low
This tool queries and retrieves publicly available information about GitHub followers. It performs a read-only operation that does not modify, execute, delete, or create any data. The data returned is already public on GitHub. The blast radius of misuse is minimal—an attacker could enumerate followers but cannot cause harm through this action alone.
From the tool's definition Tool name and description indicate 'List a GitHub user's followers' and 'Returns a page of the public accounts following a GitHub user' — these are retrieval operations with no side effects.
Attacks that exploit this kind of access
The rule that runs github_user_followers 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_user_followers, this is the rule to start with:
github_user_followers 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_user_followers call is checked against it from then on.
Questions about github_user_followers
List a GitHub user's followers. Returns a page of the public accounts following a GitHub user. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_user_followers accepts 3 parameters: page, per_page, username. Required: username. 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_user_followers: 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_user_followers 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_user_followers 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_user_followers. 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_user_followers 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