Create an issue in a project. labels is comma-separated.
AI agents use create_issue 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.
This tool creates new data (an issue) in a GitLab project, which is a Write operation. The severity is medium because: (1) issue creation could be used to spam or flood a project with unwanted content, (2) it modifies project state and could trigger notifications/workflows, but (3) it is fully reversible (issues can be deleted), and (4) it typically requires appropriate project permissions.
From the tool's definition Tool description states 'Create an issue in a project' — a create operation that adds new data to a project. Issue creation is a reversible modification (issues can be closed, deleted, or edited).
Attacks that exploit this kind of access
Create an issue in a project. labels is comma-separated. 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_issue: 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_issue 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_issue 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_issue. 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_issue is provided by the GitLab MCP server (shahabmosavi/gitlab_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →