This record as markdown: /tools/io-github-zereight-gitlab-mcp/create-issue.md
What create_issue does on Gitlab Mcp
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.
Why create_issue is rated Medium
The tool creates new data (an issue) in a reversible manner - issues can be edited, closed, or deleted later. This is a Write operation rather than Destructive since issue creation is not an irreversible action. The severity is medium because creating issues could be misused for spam, but the impact is limited to the GitLab project itself and issues can be managed/removed by maintainers.
From the tool's definition Tool name is 'create_issue' and description states 'Create a new issue'. This is a data creation operation that modifies the project state by adding a new issue.
Attacks that exploit this kind of access
The rule that runs create_issue 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_issue, this is the rule to start with:
create_issue 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_issue call is checked against it from then on.
Questions about create_issue
Create a new issue. 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 (@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