Search GitLab users by email or username. For non-admin tokens, only matches public emails.
AI agents call gitlab_search_users 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 tool retrieves user information from GitLab but does not create, modify, delete, or execute any operations. It performs a simple search query analogous to a directory lookup. The blast radius is minimal—an AI agent could gather information about GitLab users, but this information is either public or already authorized for the token in use. No side effects or irreversible actions are possible.
From the tool's definition The tool description explicitly states it "Search[es] GitLab users by email or username," which is a data retrieval operation with no modification or deletion.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access gitlab_search_users 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 gitlab_search_users:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_search_users": {}
}
}gitlab_search_users 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 GitLab users by email or username. For non-admin tokens, only matches public emails. 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 gitlab_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 Sage MCP. Nothing to install.
gitlab_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 gitlab_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 gitlab_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.
gitlab_search_users 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.