Search for users on GitHub
AI agents call search_users to retrieve information from Zerops Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Searching for users is a read-only operation that retrieves publicly available information from GitHub. The blast radius is minimal as it cannot modify data, execute code, or trigger financial transactions. It may pose a minor privacy concern if used to enumerate users systematically, but the inherent risk of the tool itself is low.
From the tool's definition The tool name is 'search_users' and description states 'Search for users on GitHub' — this is a query operation that retrieves user information without modification or side effects.
Attacks that exploit this kind of access
Search for users on GitHub. It is categorised as a Read tool in the Zerops Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerops Documentation MCP Server 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 Zerops Documentation MCP Server. 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 Zerops Documentation MCP Server MCP server (nermalcat69/zerops-mcp). 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 →