New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_search_users

Search GitLab users by email or username. For non-admin tokens, only matches public emails.

SERVERSage MCP SOURCEsagemcp/sagemcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/gitlab-search-users.md

What gitlab_search_users does on Sage MCP

AI agents call gitlab_search_users to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why gitlab_search_users is rated Low

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

Questions about gitlab_search_users

What does the gitlab_search_users tool do? +

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.

How do I enforce a policy on gitlab_search_users? +

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.

What risk level is gitlab_search_users? +

gitlab_search_users is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit gitlab_search_users? +

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.

How do I block gitlab_search_users completely? +

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.

What MCP server provides gitlab_search_users? +

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.

More on Sage, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Sage's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.