move_work_item

Move a work item to a different project

SERVERGitlab Mcp SOURCE@zereight/mcp-gitlab

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-zereight-gitlab-mcp/move-work-item.md

WHAT IT DOES

What move_work_item does on Gitlab Mcp

AI agents use move_work_item 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.

RISK

Why move_work_item is rated Medium

This action creates or modifies data in a reversible manner—the work item is relocated but not deleted, and the operation can be undone by moving it back. While the move has side effects (changing project ownership/association), it does not execute arbitrary code, destroy data, or commit financial transactions.

From the tool's definition Tool name 'move_work_item' and description 'Move a work item to a different project' indicates the tool modifies the state and location of existing data by transferring it between projects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs move_work_item 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 move_work_item, this is the rule to start with:

move_work_item Rate-limited

move_work_item 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "move_work_item": {
      "limits": [
        {
          "counter": "move_work_item_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about move_work_item

What does the move_work_item tool do? +

Move a work item to a different project. 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.

How do I enforce a policy on move_work_item? +

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

move_work_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit move_work_item? +

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

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

move_work_item 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

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →