This record as markdown: /tools/io-github-kivanccakmak-yaver/github-prs.md
What github_prs does on Yaver
AI agents call github_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 |
|---|---|---|---|
state | string | — | Filter: open, closed, merged, all (default: open) |
directory | string | — | Repo directory |
Parameters from the server's own tool schema.
Why github_prs is rated Low
This tool retrieves and lists pull request data from a GitHub repository using the gh CLI. It performs a read-only operation with no side effects, no code execution, no data modification, and no destructive capability. The potential blast radius from misuse is minimal—an attacker could enumerate PRs to gather intelligence about the codebase, but cannot modify, delete, or execute anything.
From the tool's definition Tool name 'github_prs' and description 'List pull requests from the current repo' indicate a query/retrieval operation with no modification capability.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs github_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 github_prs, this is the rule to start with:
github_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 github_prs call is checked against it from then on.
Questions about github_prs
List pull requests from the current repo (requires gh CLI). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
github_prs 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 github_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.
github_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 github_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 github_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.
github_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