omg_get_phase_info
Get information about omg-autopilot phases
This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-get-phase-info.md
What omg_get_phase_info does on Gitlab Mcp
AI agents call omg_get_phase_info 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.
Why omg_get_phase_info is rated Low
The verb 'Get information' and the passive nature of querying phase data classify this as a Read operation. There is no evidence of mutation, deletion, execution, or financial impact. The low severity reflects that retrieving phase information poses minimal risk even if accessed inappropriately.
From the tool's definition Tool name 'omg_get_phase_info' and description 'Get information about omg-autopilot phases' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs omg_get_phase_info 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_get_phase_info, this is the rule to start with:
omg_get_phase_info is read-only, so it stays allowed. 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_get_phase_info call is checked against it from then on.
Questions about omg_get_phase_info
Get information about omg-autopilot phases. It is categorised as a Read tool in the Gitlab Mcp MCP Server, which means it retrieves data without modifying state.
Register the Gitlab MCP server in PolicyLayer and add a rule for omg_get_phase_info: 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_get_phase_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the omg_get_phase_info 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_get_phase_info. 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_get_phase_info 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.
This server
Across the catalogue