Search for users on GitHub
AI agents call search_users to retrieve information from Mcp Github without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only search operation that retrieves user information from GitHub. It has no side effects, does not modify or delete data, and does not execute code or trigger external state changes. The blast radius is minimal—an agent misusing this tool could only retrieve information that is already publicly accessible on GitHub.
From the tool's definition Tool name 'search_users' and description 'Search for users on GitHub' indicate a query/search operation that retrieves publicly available user information without modifying data.
Attacks that exploit this kind of access
Search for users on GitHub. It is categorised as a Read tool in the Mcp Github MCP Server, which means it retrieves data without modifying state.
Register the Mcp 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 Mcp 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 Mcp Github MCP server (@missionsquad/mcp-github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →