Busca usuarios en GitHub por nombre, email, ubicación, etc.
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 queries GitHub's user directory without creating, modifying, deleting, or executing any operations. It returns search results on GitHub users—a read operation with minimal blast radius. Even if an AI agent misuses it by searching for users, the worst outcome is accessing public profile information, which poses no security or data integrity risk.
From the tool's definition Tool description states 'Busca usuarios' (searches users) by name, email, location, etc. The verb 'search' and the absence of any modification, deletion, or execution keywords indicate a read-only operation that retrieves publicly available user information…
Attacks that exploit this kind of access
Busca usuarios en GitHub por nombre, email, ubicación, etc. 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 (pblarismendi/mcp-github-server). 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 →