omg_select_model
Recommend the best model for a task based on complexity analysis. Maps OMC model tiers (HIGH/MEDIUM/LOW) to available VS Code Copilot models.
This record as markdown: /tools/io-github-zereight-gitlab-mcp/omg-select-model.md
What omg_select_model does on Gitlab Mcp
AI agents use omg_select_model to create or update resources in Gitlab Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gitlab Mcp environment.
Why omg_select_model is rated Medium
An AI agent can call omg_select_model faster than any human can review: one bad instruction and it creates or modifies resources in Gitlab Mcp by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs omg_select_model 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_select_model, this is the rule to start with:
omg_select_model 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every omg_select_model call is checked against it from then on.
Questions about omg_select_model
Recommend the best model for a task based on complexity analysis. Maps OMC model tiers (HIGH/MEDIUM/LOW) to available VS Code Copilot models. It is categorised as a Write tool in the Gitlab Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Gitlab MCP server in PolicyLayer and add a rule for omg_select_model: 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_select_model is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the omg_select_model 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_select_model. 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_select_model 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