New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

gitlab_issue_create

Open a GitLab issue.

SERVERYaver SOURCEyaver-cli
Medium RISK CLASS
Category Write
Parameters 41 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/gitlab-issue-create.md

What gitlab_issue_create does on Yaver

AI agents use gitlab_issue_create to create or update resources in Yaver, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Yaver environment.

ParameterTypeRequiredDescription
title string Yes
labels array
directory string
description string

Parameters from the server's own tool schema.

Why gitlab_issue_create is rated Medium

Opening/creating a GitLab issue is a reversible write operation that creates data in an external system. It does not execute arbitrary code, delete data, or move money. The severity is medium because creating issues could be abused to spam a project or create misleading records, but the action is reversible and not destructive.

From the tool's definition Tool name contains 'create' and description states 'Open a GitLab issue', which creates a new persistent record in GitLab.

Risk signalsAccepts file system path (directory)

Questions about gitlab_issue_create

What does the gitlab_issue_create tool do? +

Open a GitLab issue. It is categorised as a Write tool in the Yaver MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does gitlab_issue_create accept? +

gitlab_issue_create accepts 4 parameters: title, labels, directory, description. Required: title. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on gitlab_issue_create? +

Register the Yaver MCP server in PolicyLayer and add a rule for gitlab_issue_create: 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 Yaver. Nothing to install.

What risk level is gitlab_issue_create? +

gitlab_issue_create is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit gitlab_issue_create? +

Yes. Add a rate_limit block to the gitlab_issue_create 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.

How do I block gitlab_issue_create completely? +

Set action: deny in the PolicyLayer policy for gitlab_issue_create. 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.

What MCP server provides gitlab_issue_create? +

gitlab_issue_create is provided by the Yaver MCP server (yaver-cli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Yaver, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Yaver's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.