This record as markdown: /tools/io-github-kivanccakmak-yaver/github-workflow-run.md
What github_workflow_run does on Yaver
AI agents invoke github_workflow_run to trigger actions in Yaver. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
ref | string | — | Branch/tag/SHA to run against |
inputs | object | — | |
workflow | string | Yes | Filename (ci.yml) or workflow display name |
directory | string | — |
Parameters from the server's own tool schema.
Why github_workflow_run is rated High
This tool executes code in a GitHub Actions environment, which can modify repositories, deploy applications, run tests, or perform other automated tasks. While workflows themselves are developer-defined, triggering them represents an Execute action whose effects depend on what the target workflow does.
From the tool's definition Tool name 'github_workflow_run' combined with description 'Trigger a GitHub Actions workflow_dispatch run' indicates execution of external CI/CD pipelines. The 'workflow_dispatch' event type explicitly allows triggering arbitrary GitHub Actions workflows.
Risk signalsAccepts file system path (directory)
Attacks that exploit this kind of access
The rule that runs github_workflow_run 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_workflow_run, this is the rule to start with:
github_workflow_run stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_workflow_run call is checked against it from then on.
Questions about github_workflow_run
Trigger a GitHub Actions workflow_dispatch run. It is categorised as a Execute tool in the Yaver MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
github_workflow_run accepts 4 parameters: ref, inputs, workflow, directory. Required: workflow. 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_workflow_run: 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_workflow_run is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the github_workflow_run 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_workflow_run. 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_workflow_run 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.
Across the catalogue