GitLab Protection Rules (BYOK)

GitLab Protection Rules (BYOK) — connector documentation

• MCP endpoint: https://byok-gitlab-protection.connectorbay.com/mcp
• REST API: POST https://byok-gitlab-protection.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-gitlab-protection.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own GitLab Protection Rules personal access token (read_api scope), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-gitlab-protection.connectorbay.com/health · Tool schemas: https://byok-gitlab-protection.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-gitlab-protection · agent@connectorbay.com

What GitLab Protection Rules (BYOK) is for

GitLab Protection Rules (BYOK) lets an AI assistant read your own GitLab Protection Rules data through the GitLab Protection Rules API with a key you supply (personal access token (read_api scope)). Read-only: 10 tools (list_protected_branches, get_protected_branch, list_protected_tags, get_protected_tag, list_protected_environments, get_protected_environment, get_project_approval_settings, list_project_approval_rules, get_project_approval_rule, get_project_push_rules). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to gitlab.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitLab Protection Rules. GitLab Protection Rules and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which branches are protected in gitlab-org/gitlab and who can merge to them?"
• "Is force push allowed on main in gitlab-org/gitlab?"
• "Which tags are protected in gitlab-org/gitlab?"
• "Who can create release tags in gitlab-org/gitlab?"
• "Which environments of gitlab-org/gitlab are protected and how many approvals does production need?"
• "Who may deploy to production in gitlab-org/gitlab?"

What it does

• list_protected_branches: List a project's protected branches and wildcards with force-push and code owner settings and who may push or merge. Each entry has an access level (0 none, 30 developer, 40 maintainer) and may name a user ID, group ID or deploy key ID.
• get_protected_branch: Get one protected branch or wildcard rule by its name or pattern, with push and merge permissions.
• list_protected_tags: List a project's protected tags and wildcards with who may create them. Each entry has an access level (0 none, 30 developer, 40 maintainer) and may name a user ID, group ID or deploy key ID.
• get_protected_tag: Get one protected tag or wildcard rule by its name or pattern, with who may create matching tags.
• list_protected_environments: List a project's protected environments with the access levels allowed to deploy and the number of approvals required (Premium and Ultimate).
• get_protected_environment: Get one protected environment by name with its deploy access levels and required approval count.
• get_project_approval_settings: Get a project's merge request approval settings: author self-approval, committer approval, reset on push and reauthentication.
• list_project_approval_rules: List a project's merge request approval rules with rule type, report type and number of approvals required (approver names are left out).
• get_project_approval_rule: Get one merge request approval rule of a project by ID (approver names are left out).
• get_project_push_rules: Get a project's push rules: branch name and commit message patterns, file size limit, secret prevention and signed commit requirements (Premium and Ultimate). Returns the text null when none are set.

BYOK key

You bring your own GitLab Protection Rules personal access token (read_api scope) (https://gitlab.com/-/user_settings/personal_access_tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to gitlab.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://docs.gitlab.com/api/protected_branches/ (the API this connector calls, with a BYOK key)

Live from the GitLab Protection Rules API (gitlab.com) with a BYOK key; documentation: https://docs.gitlab.com/api/protected_branches/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitLab Protection Rules. GitLab Protection Rules and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your GitLab Protection Rules account.

Built for: Worldwide. Languages: English.

GitLab Protection Rules (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What GitLab Protection Rules (BYOK) is. GitLab Protection Rules (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own GitLab Protection Rules data: Read a GitLab.com project's protected branches, protected tags, protected environments, approval rules and push rules with your own personal access token. You bring your own GitLab Protection Rules personal access token (read_api scope); the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one GitLab Protection Rules call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to gitlab.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If GitLab Protection Rules rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What GitLab Protection Rules receives. The request we make on your behalf, including the key and the arguments, under GitLab Protection Rules's own terms and privacy policy. GitLab Protection Rules acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer GitLab Protection Rules gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your GitLab Protection Rules data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. GitLab Protection Rules (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at GitLab Protection Rules at any time to end all access.

Children. GitLab Protection Rules (BYOK) is a general-audience service operated by the adult using the assistant, under GitLab Protection Rules's own age rules.

Changes. We will post changes here with a new effective date.

GitLab Protection Rules (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the GitLab Protection Rules (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. GitLab Protection Rules (BYOK) provides: Read a GitLab.com project's protected branches, protected tags, protected environments, approval rules and push rules with your own personal access token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own GitLab Protection Rules credentials and only access data you are allowed to access. GitLab Protection Rules's terms apply to your use of GitLab Protection Rules; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by GitLab Protection Rules. GitLab Protection Rules and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data GitLab Protection Rules returns, lightly trimmed; it may be incomplete, delayed or changed by GitLab Protection Rules. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your GitLab Protection Rules account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent GitLab Protection Rules's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; GitLab Protection Rules may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your GitLab Protection Rules key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action GitLab Protection Rules takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-gitlab-protection

GitLab Protection Rules (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-gitlab-protection.connectorbay.com/mcp
• REST API: https://byok-gitlab-protection.connectorbay.com/openapi.json
• Live status: https://byok-gitlab-protection.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. GitLab Protection Rules (BYOK) never asks for them.