github_search_users
Search public GitHub users. Searches public GitHub users (developer discovery). Unauthenticated search is rate limited to roughly 10 requests per minute.
This record as markdown: /tools/crawlora-mcp/github-search-users.md
What github_search_users does on Crawlora
AI agents call github_search_users 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 |
|---|---|---|---|
q | string | Yes | GitHub user search query |
page | integer | — | Page number |
sort | string | — | Sort field |
order | string | — | Sort order |
per_page | integer | — | Results per page (max 100) |
Parameters from the server's own tool schema.
Why github_search_users is rated Low
This tool queries publicly available GitHub user information for discovery purposes. It retrieves data without creating, modifying, deleting, or executing any operations. The unauthenticated rate limit is typical of read-only APIs. No destructive, financial, or code execution capability is present.
From the tool's definition 'Search public GitHub users' and 'Searches public GitHub users (developer discovery)' — retrieves public data with no modification or side effects. Rate limiting indicates read-only API usage.
Attacks that exploit this kind of access
The rule that runs github_search_users 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_search_users, this is the rule to start with:
github_search_users 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_search_users call is checked against it from then on.
Questions about github_search_users
Search public GitHub users. Searches public GitHub users (developer discovery). Unauthenticated search is rate limited to roughly 10 requests per minute. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
github_search_users accepts 5 parameters: q, page, sort, order, per_page. Required: q. 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_search_users: 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_search_users 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_search_users 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_search_users. 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_search_users 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