github_ci_status
Show recent GitHub Actions workflow runs and their status (requires gh CLI).
This record as markdown: /tools/io-github-kivanccakmak-yaver/github-ci-status.md
What github_ci_status does on Yaver
AI agents call github_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 |
|---|---|---|---|
directory | string | — | Repo directory |
Parameters from the server's own tool schema.
Why github_ci_status is rated Low
This tool queries and displays the status of existing GitHub Actions workflows. It retrieves data about CI/CD pipeline execution history without creating, modifying, deleting, or triggering any changes. The dependency on 'gh CLI' for authentication does not elevate it beyond Read, as the tool itself performs no side effects.
From the tool's definition Tool description states it 'Show[s] recent GitHub Actions workflow runs and their status' - a pure retrieval operation with no modification, deletion, or execution capability.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs github_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 github_ci_status, this is the rule to start with:
github_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 github_ci_status call is checked against it from then on.
Questions about github_ci_status
Show recent GitHub Actions workflow runs and their status (requires gh CLI). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
github_ci_status accepts 1 parameter: 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_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.
github_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 github_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 github_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.
github_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