Search for GitHub users (returns minimal data).
AI agents call search_users to retrieve information from GitHub and AlphaVantage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves publicly available GitHub user information without creating, modifying, deleting, or executing any operations. It is a read-only search function with minimal blast radius if misused by an AI agent.
From the tool's definition Tool name and description indicate 'Search for GitHub users (returns minimal data)' — a query operation with no data modification or side effects.
Attacks that exploit this kind of access
Search for GitHub users (returns minimal data). It is categorised as a Read tool in the GitHub and AlphaVantage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the GitHub and AlphaVantage 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 GitHub and AlphaVantage 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 GitHub and AlphaVantage MCP Server MCP server (uditdev21/mcp-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 →