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.

SERVERCrawlora SOURCEcrawlora-mcp
Low RISK CLASS
Category Read
Parameters 120 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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

Even though datasets_github_users_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Risk signalsHigh parameter count (30 properties)

Questions about datasets_github_users_search

What does the datasets_github_users_search tool do? +

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.

What parameters does datasets_github_users_search accept? +

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.

How do I enforce a policy on datasets_github_users_search? +

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.

What risk level is datasets_github_users_search? +

datasets_github_users_search is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit datasets_github_users_search? +

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.

How do I block datasets_github_users_search completely? +

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.

What MCP server provides datasets_github_users_search? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crawlora's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.