search_repositories

THE RISK

Low Risk

Why search_repositories needs a policy

This tool retrieves and lists GitLab projects matching search criteria. It performs a read-only operation with no ability to modify, create, delete, or execute operations. The blast radius of misuse is minimal—an agent could only discover repositories it may already have access to or that are public. No data is modified, destroyed, or financial transactions triggered.

From the tool's definition Tool name is 'search_repositories' and description states 'Search for GitLab projects' — a query operation with no side effects.

Documented attack patterns abuse exactly the kind of access search_repositories gives an agent:

POLICY

How to control search_repositories

PolicyLayer is an MCP gateway — it sits between your AI agents and GitLab MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_repositories:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_repositories": {}
  }
}

search_repositories is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register GitLab MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More GitLab MCP Server tools

Write create_issue Create a new issue in a GitLab project Write create_merge_request Create a new merge request in a GitLab project Write create_merge_request_line_comment create_merge_request_line_comment Write create_or_update_file Create or update a file in a GitLab project Write create_repository Create a new GitLab project Read get_file_contents Get the contents of a file from a GitLab project Read get_merge_request_diff Get the diff of a merge request to find valid line positions for comments.

All 8 GitLab MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about search_repositories

What does the search_repositories tool do? +

Search for GitLab projects. It is categorised as a Read tool in the GitLab MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_repositories? +

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

What risk level is search_repositories? +

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

Can I rate-limit search_repositories? +

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

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

search_repositories is provided by the GitLab MCP Server MCP server (radostkali/gitlab-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every GitLab MCP Server tool call.

Start from GitLab MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →