omg_list_active

List all currently active OMG modes

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-list-active.md

WHAT IT DOES

What omg_list_active does on Gitlab Mcp

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

RISK

Why omg_list_active is rated Low

This tool retrieves or queries data about active OMG (likely a GitLab feature/mode) with no side effects. It performs a simple listing/retrieval operation typical of Read category tools. Severity is low as listing status information has minimal blast radius even if misused by an AI agent.

From the tool's definition Tool name contains 'list' and description states 'List all currently active OMG modes', which retrieves information without modification or execution of operations.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs omg_list_active safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gitlab Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For omg_list_active, this is the rule to start with:

omg_list_active Allowed

omg_list_active is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every omg_list_active call is checked against it from then on.

FAQ

Questions about omg_list_active

What does the omg_list_active tool do? +

List all currently active OMG modes. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on omg_list_active? +

Register the Gitlab MCP server in PolicyLayer and add a rule for omg_list_active: 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.

What risk level is omg_list_active? +

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

Can I rate-limit omg_list_active? +

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

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

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

KEEP EXPLORING

More on Gitlab, and thousands of servers like it.

This server

All 215 Gitlab tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →