AI agents use gitlab_create_merge_request to create or update resources in Sage MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sage MCP environment.
This tool creates a new merge request, which is a reversible modification to a GitLab repository's state. While not destructive (can be undone), it has higher severity than a simple Read operation because it modifies repository metadata and workflow state, potentially triggering CI/CD pipelines, notifications, and affecting team collaboration processes.
From the tool's definition Tool name 'gitlab_create_merge_request' and description 'Create a new merge request' indicate the tool creates a new entity (merge request) in GitLab, which is a reversible Write operation.
Documented attack patterns abuse exactly the kind of access gitlab_create_merge_request gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_create_merge_request:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_create_merge_request": {
"limits": [
{
"counter": "gitlab_create_merge_request_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gitlab_create_merge_request 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.
Free to start. No card required.
Create a new merge request. It is categorised as a Write tool in the Sage MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sage MCP server in PolicyLayer and add a rule for gitlab_create_merge_request: 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 Sage MCP. Nothing to install.
gitlab_create_merge_request 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 gitlab_create_merge_request 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 gitlab_create_merge_request. 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.
gitlab_create_merge_request is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.