omg_next_phase
Advance the omg-autopilot workflow to the next phase. Returns the new phase details.
This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-next-phase.md
What omg_next_phase does on Gitlab Mcp
AI agents invoke omg_next_phase to trigger actions in Gitlab Mcp. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why omg_next_phase is rated High
This tool advances an automated workflow (omg-autopilot) to its next phase, which constitutes triggering an external operation whose effects depend on the current workflow state. It is not a simple read or write, but an execution of a workflow transition that could have broad downstream effects (pipeline runs, deployments, etc.).
From the tool's definition 'Advance the omg-autopilot workflow to the next phase' — triggers an external workflow state transition operation
Attacks that exploit this kind of access
The rule that runs omg_next_phase 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_next_phase, this is the rule to start with:
omg_next_phase stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every omg_next_phase call is checked against it from then on.
Questions about omg_next_phase
Advance the omg-autopilot workflow to the next phase. Returns the new phase details. It is categorised as a Execute tool in the Gitlab Mcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Gitlab MCP server in PolicyLayer and add a rule for omg_next_phase: 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.
omg_next_phase is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the omg_next_phase 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.
Set action: deny in the PolicyLayer policy for omg_next_phase. 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.
omg_next_phase 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.
More on Gitlab, and thousands of servers like it.
Across the catalogue