datasets_github_users_search
Search the GitHub users dataset. Searches enriched public GitHub user profiles stored in a search index. influence_tier enum: nano, micro, mid, macro, mega. Sort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc.
This record as markdown: /tools/crawlora-mcp/datasets-github-users-search.md
What datasets_github_users_search does on Crawlora
AI agents call datasets_github_users_search 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 | — | Full-text query over login, name, company, bio and location, max 256 characters |
lat | number | — | Latitude for radius filtering or distance sort |
lon | number | — | Longitude for radius filtering or distance sort |
city | string | — | Exact geocoded city filter, max 128 characters |
page | integer | — | Page number, defaults to 1 |
sort | string | — | Sort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc |
login | string | — | Exact login filter, max 128 characters |
state | string | — | Exact geocoded state filter, max 128 characters |
domain | string | — | Interest-domain tag filter (e.g. ml-ai, web, devops), max 128 characters |
is_bot | boolean | — | Bot filter (normally false; the crawl skips bots) |
is_org | boolean | — | Organization filter (normally false; the crawl indexes individuals) |
company | string | — | Exact normalized-company filter, max 128 characters |
Parameters from the server's own tool schema.
Why datasets_github_users_search is rated Low
This tool retrieves and queries publicly available GitHub user profile data with various search and sort parameters. It has no side effects, does not execute code, does not modify data, and does not involve financial transactions. It is a pure read operation that falls squarely within the Read category with low severity since it only accesses public data.
From the tool's definition Tool description explicitly states 'Search the GitHub users dataset' and 'Searches enriched public GitHub user profiles stored in a search index' with sorting and filtering options. No modification, deletion, execution, or financial operations are described.
Risk signalsHigh parameter count (30 properties)
Attacks that exploit this kind of access
The rule that runs datasets_github_users_search 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 datasets_github_users_search, this is the rule to start with:
datasets_github_users_search 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 datasets_github_users_search call is checked against it from then on.
Questions about datasets_github_users_search
Search the GitHub users dataset. Searches enriched public GitHub user profiles stored in a search index. influence_tier enum: nano, micro, mid, macro, mega. Sort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_github_users_search accepts 12 parameters: q, lat, lon, city, page, sort, login, state, domain, is_bot, is_org, company. 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 datasets_github_users_search: 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.
datasets_github_users_search 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 datasets_github_users_search 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 datasets_github_users_search. 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.
datasets_github_users_search 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