github_search_users

Search users (people / organizations).

SERVERGithub SOURCEdkeeno/github-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dkeeno-github-mcp-server/github-search-users.md

WHAT IT DOES

What github_search_users does on Github

AI agents call github_search_users to retrieve information from Github without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why github_search_users is rated Low

This tool retrieves user/organization data from GitHub's public API without creating, modifying, deleting, or executing any operations. It has no blast radius if misused by an AI agent—querying public user information poses minimal security risk. It falls squarely into the Read category.

From the tool's definition Tool name is 'github_search_users' and description states it 'Search users (people / organizations)'. Searching is a read-only operation that retrieves public information without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs github_search_users safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Github, 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 Allowed

github_search_users is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "github_search_users": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Github, apply this rule, and every github_search_users call is checked against it from then on.

FAQ

Questions about github_search_users

What does the github_search_users tool do? +

Search users (people / organizations). It is categorised as a Read tool in the Github MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on github_search_users? +

Register the Github 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 Github. Nothing to install.

What risk level is github_search_users? +

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

Can I rate-limit github_search_users? +

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.

How do I block github_search_users completely? +

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.

What MCP server provides github_search_users? +

github_search_users is provided by the Github MCP server (dkeeno/github-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Github, and thousands of servers like it.

This server

All 69 Github tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →