create_work_item
Create a work item (issue, task, incident, epic, etc.) with full field support
This record as markdown: /tools/io-github-zereight-gitlab-mcp/create-work-item.md
What create_work_item does on Gitlab Mcp
AI agents use create_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.
Why create_work_item is rated Medium
This tool creates new work items in GitLab, which modifies project state by adding persistent records. Creation is reversible (items can be deleted), so it falls under Write rather than Destructive. The blast radius is medium: an AI agent could spam creation of work items, pollute the project backlog, or create misleading tasks, but the impact is limited to project metadata and can be recovered.
From the tool's definition Tool name 'create_work_item' and description 'Create a work item (issue, task, incident, epic, etc.)' explicitly indicate data creation.
Attacks that exploit this kind of access
The rule that runs create_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 create_work_item, this is the rule to start with:
create_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gitlab Mcp, apply this rule, and every create_work_item call is checked against it from then on.
Questions about create_work_item
Create a work item (issue, task, incident, epic, etc.) with full field support. 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 create_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.
create_work_item 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 create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
More on Gitlab, and thousands of servers like it.
This server
Across the catalogue