datasets_github_users_facets
Facet the GitHub users dataset. Returns terms aggregation counts for the GitHub users dataset. Facet enum: influence_tier, type, country, country_code, state, city, domains, company, reachable, has_email, has_twitter, has_blog, active_90d, hireable, is_org, is_bot, is_suspected_automation. influe...
This record as markdown: /tools/crawlora-mcp/datasets-github-users-facets.md
What datasets_github_users_facets does on Crawlora
AI agents call datasets_github_users_facets 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 |
lon | number | — | Longitude for radius filtering |
city | string | — | Exact geocoded city filter, max 128 characters |
sort | string | — | Sort enum: relevance, rank_score_desc, followers_desc, account_age_desc, account_age_asc, distance_asc |
facet | string | Yes | Facet enum: influence_tier, type, country, country_code, state, city, domains, company, reachable, has_email, has_twitter, has_blog, active_90d, hireable, is_or |
login | string | — | Exact login filter, max 128 characters |
state | string | — | Exact geocoded state filter, max 128 characters |
domain | string | — | Interest-domain tag filter, max 128 characters |
is_bot | boolean | — | Bot filter |
is_org | boolean | — | Organization filter |
company | string | — | Exact normalized-company filter, max 128 characters |
Parameters from the server's own tool schema.
Why datasets_github_users_facets is rated Low
This tool only queries and retrieves aggregated facet/count data from a GitHub users dataset. It has no side effects, does not modify any data, and only returns statistical summaries (terms aggregation counts). The severity is low as it returns aggregate counts rather than individual user data.
From the tool's definition Facet the GitHub users dataset. Returns terms aggregation counts for the GitHub users dataset.
Risk signalsHigh parameter count (29 properties)
Attacks that exploit this kind of access
The rule that runs datasets_github_users_facets 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_facets, this is the rule to start with:
datasets_github_users_facets 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_facets call is checked against it from then on.
Questions about datasets_github_users_facets
Facet the GitHub users dataset. Returns terms aggregation counts for the GitHub users dataset. Facet enum: influence_tier, type, country, country_code, state, city, domains, company, reachable, has_email, has_twitter, has_blog, active_90d, hireable, is_org, is_bot, is_suspected_automation. influence_tier enum: nano, micro, mid, macro, mega. Suspected-automation records are excluded by default unless is_suspected_automation is set. It is categorised as a Read tool in the Crawlora MCP Server, which means it retrieves data without modifying state.
datasets_github_users_facets accepts 12 parameters: q, lat, lon, city, sort, facet, login, state, domain, is_bot, is_org, company. Required: facet. 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_facets: 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_facets 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_facets 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_facets. 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_facets 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