search
AI agents call search to retrieve information from GitLab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'search' and its position among sibling tools (which include create, approve, cancel, and comment operations) indicates this is a data retrieval function. Without a description, confidence is reduced, but search operations are generally read-only with minimal blast radius. If misused by an agent, it could only leak information available to the authenticated user's token scope, not modify or delete anything.
From the tool's definition Tool name 'search' with empty description suggests a query/retrieval operation typical of Read category. In GitLab API context, search usually queries projects, issues, or merge requests without modifying state.
Attacks that exploit this kind of access
search. It is categorised as a Read tool in the GitLab MCP MCP Server, which means it retrieves data without modifying state.
Register the GitLab MCP server in PolicyLayer and add a rule for search: 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 GitLab MCP. Nothing to install.
search 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 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. 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 is provided by the GitLab MCP server (shahabmosavi/gitlab_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 →