Create a new iteration (sprint) in a group. start_date and due_date are required (YYYY-MM-DD). dry_run=true by default.
AI agents use create_iteration to create or update resources in Mcp Gitlab — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Gitlab environment.
Creating an iteration is a write operation that adds new structured data to a group. It is reversible (unlike deletion) and does not execute arbitrary code, trigger pipelines, or move money. The dry_run=true default provides safety but does not change the categorization of the actual operation.
From the tool's definition "Create a new iteration (sprint) in a group" — this creates a new data object in GitLab. The tool modifies project/group state by adding a sprint, which is reversible (iterations can be deleted or edited).
Attacks that exploit this kind of access
Create a new iteration (sprint) in a group. start_date and due_date are required (YYYY-MM-DD). dry_run=true by default. It is categorised as a Write tool in the Mcp Gitlab MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Gitlab MCP server in PolicyLayer and add a rule for create_iteration: 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 Mcp Gitlab. Nothing to install.
create_iteration 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_iteration 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_iteration. 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_iteration is provided by the Mcp Gitlab MCP server (wanadev/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 →