Search for users on GitHub
AI agents call search_users to retrieve information from Server Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
q | string | Yes | |
page | number | — | |
sort | string | — | |
order | string | — | |
per_page | number | — |
Parameters from the server's own tool schema.
This tool performs a search query to retrieve user information from GitHub. It has no side effects—it does not create, modify, or delete data. It is a straightforward read operation that returns search results based on query parameters. The blast radius of misuse is minimal; an attacker could enumerate GitHub users but cannot access private data, execute code, or cause irreversible harm through this operation alone.
From the tool's definition Tool name 'search_users' and description 'Search for users on GitHub' indicate a query operation that retrieves user data without modification.
Attacks that exploit this kind of access
Search for users on GitHub. It is categorised as a Read tool in the Server Github MCP Server, which means it retrieves data without modifying state.
search_users accepts 5 parameters: q, page, sort, order, per_page. Required: q. The full parameter table on this page comes from the server's own tool schema.
Register the Server Github MCP server in PolicyLayer and add a rule for 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 Server Github. Nothing to install.
search_users 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 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.
Set action: deny in the PolicyLayer policy for 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.
search_users is provided by the Server Github MCP server (@iflow-mcp/server-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
search_users is one line of Server Github's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →