git_prs
List pull requests or merge requests 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-prs.md
What git_prs does on Yaver
AI agents call git_prs 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, merged, or all |
provider | string | — | auto, github, or gitlab |
directory | string | — | Repo directory |
Parameters from the server's own tool schema.
Why git_prs is rated Low
This tool queries and lists existing pull requests from a repository. It performs no creation, modification, deletion, or execution of code. The read-only nature and lack of side effects clearly place it in the Read category. Severity is low because listing PRs exposes only metadata typically visible to authorized repository members, with minimal blast radius.
From the tool's definition Tool name 'git_prs' and description explicitly states 'List pull requests' — a retrieval operation with no side effects. Payload parameters (provider, directory, state) are all query filters, not mutations.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_prs 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_prs, this is the rule to start with:
git_prs 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_prs call is checked against it from then on.
Questions about git_prs
List pull requests or merge requests 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_prs 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_prs: 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_prs 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_prs 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_prs. 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_prs 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