This record as markdown: /tools/io-github-kivanccakmak-yaver/gitlab-issues.md
What gitlab_issues does on Yaver
AI agents call gitlab_issues to retrieve information from Yaver without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
state | string | — | |
directory | string | — |
Parameters from the server's own tool schema.
Why gitlab_issues is rated Low
This tool queries and retrieves GitLab issue data without creating, modifying, deleting, or executing any operations. Listing issues is a straightforward data retrieval action with no risk of data mutation or external execution. Severity is low because exposure of this tool to an AI agent presents minimal risk—viewing issue metadata is non-destructive and typically already accessible to authenticated users.
From the tool's definition Tool name is 'gitlab_issues' and description states 'List GitLab issues.' The verb 'List' explicitly indicates a read-only retrieval operation with no side effects.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs gitlab_issues safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Yaver, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gitlab_issues, this is the rule to start with:
gitlab_issues is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every gitlab_issues call is checked against it from then on.
Questions about gitlab_issues
List GitLab issues. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
gitlab_issues accepts 2 parameters: state, directory. The full parameter table on this page comes from the server's own tool schema.
Register the Yaver MCP server in PolicyLayer and add a rule for gitlab_issues: 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.
gitlab_issues is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the gitlab_issues 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_issues. 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_issues 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.
This server
Across the catalogue