convert_work_item_type
Convert a work item to a different type
This record as markdown: /tools/io-github-zereight-gitlab-mcp/convert-work-item-type.md
What convert_work_item_type does on Gitlab Mcp
AI agents use convert_work_item_type 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 convert_work_item_type is rated Medium
Converting a work item type is a modification operation that alters metadata and potentially workflow state, but does not create or delete data irreversibly. It is reversible and has moderate blast radius in a team context (could confuse tracking if applied to the wrong item), making it Write with medium severity rather than higher categories.
From the tool's definition Tool description states 'Convert a work item to a different type' — this modifies the type attribute of an existing work item, changing its classification or structure. The action is reversible (can be converted back to the original type).
Attacks that exploit this kind of access
The rule that runs convert_work_item_type 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 convert_work_item_type, this is the rule to start with:
convert_work_item_type 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 convert_work_item_type call is checked against it from then on.
Questions about convert_work_item_type
Convert a work item to a different type. 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 convert_work_item_type: 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.
convert_work_item_type 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 convert_work_item_type 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 convert_work_item_type. 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.
convert_work_item_type 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