Search for GitHub users by email address. Only matches users who have set their email as public on GitHub.
AI agents call github_search_users_by_email to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation with no side effects. It queries publicly available information that users have explicitly made public. The search returns user data without any ability to modify repositories, trigger actions, or access private information.
From the tool's definition Tool description states 'Search for GitHub users by email address' with no modification, deletion, or code execution. It retrieves public email information that users have voluntarily exposed on GitHub profiles.
Documented attack patterns abuse exactly the kind of access github_search_users_by_email gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for github_search_users_by_email:
{
"version": "1",
"default": "deny",
"tools": {
"github_search_users_by_email": {}
}
}github_search_users_by_email is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search for GitHub users by email address. Only matches users who have set their email as public on GitHub. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for github_search_users_by_email: 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 Sage MCP. Nothing to install.
github_search_users_by_email 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 github_search_users_by_email 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 github_search_users_by_email. 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.
github_search_users_by_email is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.