datasets_github_users_facets

SERVERCrawlora SOURCEcrawlora-mcp

Medium RISK CLASS

Category Write

Parameters 121 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/crawlora-mcp/datasets-github-users-facets.md

WHAT IT DOES

What datasets_github_users_facets does on Crawlora

AI agents use datasets_github_users_facets to create or update resources in Crawlora, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Crawlora environment.

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.

RISK

Why datasets_github_users_facets is rated Medium

An AI agent can call datasets_github_users_facets faster than any human can review: one bad instruction and it creates or modifies resources in Crawlora by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (29 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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 Rate-limited

datasets_github_users_facets stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datasets_github_users_facets": {
      "limits": [
        {
          "counter": "datasets_github_users_facets_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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.

FAQ

Questions about datasets_github_users_facets

What does the datasets_github_users_facets tool do? +

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 Write tool in the Crawlora MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does datasets_github_users_facets accept? +

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.

How do I enforce a policy on datasets_github_users_facets? +

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.

What risk level is datasets_github_users_facets? +

datasets_github_users_facets is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit datasets_github_users_facets? +

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.

How do I block datasets_github_users_facets completely? +

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.

What MCP server provides datasets_github_users_facets? +

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.

KEEP EXPLORING

More on Crawlora, and thousands of servers like it.

This server

All 728 Crawlora tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →