search_merge_requests

Search merge requests by full-text query within a project or group. Maps to GET /:scope/:id/search?scope=merge_requests.

Server Mcp Gitlab wanadev/gitlab-mcp
Category Read
Risk class Low
Parameters 00 required

What search_merge_requests does on Mcp Gitlab

AI agents call search_merge_requests to retrieve information from Mcp Gitlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why search_merge_requests needs a policy

search_merge_requests retrieves and queries merge request data without side effects. It does not create, modify, delete, or execute operations. The blast radius of misuse is minimal—an agent could only discover or enumerate merge requests it may or may not have permission to view, which is a standard read risk. This clearly falls under the Read category at low severity.

From the tool's definition Tool performs a search operation via GET request mapping to a read-only API endpoint. Description states "Search merge requests by full-text query" with no modification, deletion, or execution capabilities.

Questions about search_merge_requests

What does the search_merge_requests tool do? +

Search merge requests by full-text query within a project or group. Maps to GET /:scope/:id/search?scope=merge_requests. It is categorised as a Read tool in the Mcp Gitlab MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_merge_requests? +

Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for search_merge_requests: 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 Mcp Gitlab. Nothing to install.

What risk level is search_merge_requests? +

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

Can I rate-limit search_merge_requests? +

Yes. Add a rate_limit block to the search_merge_requests 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 search_merge_requests completely? +

Set action: deny in the PolicyLayer policy for search_merge_requests. 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 search_merge_requests? +

search_merge_requests is provided by the Mcp Gitlab MCP server (wanadev/gitlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.