share_project_with_group · GitLab MCP Server MCP

WHAT IT DOES

What share_project_with_group does on GitLab MCP Server

AI agents use share_project_with_group to create or update resources in GitLab MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your GitLab MCP Server environment.

WHY IT NEEDS A POLICY

Why share_project_with_group needs a policy

Based on the tool name, this likely shares a GitLab project with a group, granting access permissions — a reversible write operation. However, the empty description lowers confidence significantly. Sharing a project modifies access control settings, which is a Write action. Severity is medium because misconfigured sharing could expose a project to unintended groups.

From the tool's definition Tool name: share_project_with_group; description is empty/uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

share_project_with_group Rate-limited

share_project_with_group stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "share_project_with_group": {
      "limits": [
        {
          "counter": "share_project_with_group_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches GitLab MCP Server, so you can run agents against it safely.

FAQ

Questions about share_project_with_group

What does the share_project_with_group tool do? +

share_project_with_group. It is categorised as a Write tool in the GitLab MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on share_project_with_group? +

Register the GitLab MCP Server MCP server in PolicyLayer and add a rule for share_project_with_group: 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 share_project_with_group? +

share_project_with_group is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit share_project_with_group? +

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

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

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