git_ci_status
Show recent CI status from the current repo via a neutral git surface. Payload {provider?: auto|github|gitlab, directory?}.
This record as markdown: /tools/io-github-kivanccakmak-yaver/git-ci-status.md
What git_ci_status does on Yaver
AI agents call git_ci_status 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 |
|---|---|---|---|
provider | string | — | auto, github, or gitlab |
directory | string | — | Repo directory |
Parameters from the server's own tool schema.
Why git_ci_status is rated Low
This tool retrieves and displays CI status information from a repository without making any changes, executing code, or performing side effects. It is a straightforward query operation that fits the Read category. The low severity reflects that viewing CI status poses minimal risk—it cannot modify code, trigger deployments, delete data, or commit financial transactions.
From the tool's definition Tool description: 'Show recent CI status from the current repo via a neutral git surface.' The verb 'Show' and the phrase 'via a neutral git surface' indicate read-only querying of CI status data with no modification, creation, or execution of operations.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs git_ci_status 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_ci_status, this is the rule to start with:
git_ci_status 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_ci_status call is checked against it from then on.
Questions about git_ci_status
Show recent CI status from the current repo via a neutral git surface. Payload {provider?: auto|github|gitlab, directory?}. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
git_ci_status accepts 2 parameters: 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_ci_status: 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_ci_status 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_ci_status 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_ci_status. 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_ci_status 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