git_issues
List issues from the current repo via a neutral git surface. Payload {provider?: auto|github|gitlab, directory?, state?}.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-issues.md
What git_issues does on Yaver
AI agents call git_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 |
|---|---|---|---|
limit | integer | — | Advisory limit (max 50) |
state | string | — | open/opened, closed, or all |
provider | string | — | auto, github, or gitlab |
directory | string | — | Repo directory |
Parameters from the server's own tool schema.
Why git_issues is rated Low
This tool retrieves and lists issue data from a git repository without creating, modifying, deleting, or executing any operations. It is a straightforward read operation with minimal blast radius—an AI agent misusing it would only retrieve information already stored in the repo, with no side effects on the codebase or infrastructure.
From the tool's definition Tool name 'git_issues' and description 'List issues from the current repo' indicates querying/retrieval of issue data with no modification capability. The payload parameters (provider, directory, state) are all filters for read operations.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_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 git_issues, this is the rule to start with:
git_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 git_issues call is checked against it from then on.
Questions about git_issues
List issues from the current repo via a neutral git surface. Payload {provider?: auto|github|gitlab, directory?, state?}. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_issues accepts 4 parameters: limit, state, provider, 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 git_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.
git_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 git_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 git_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.
git_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