publish_ci_dispatch
Alias of publish_run for CI-oriented clients. Use allow_github_fallback=true when you want GitHub dispatch as the fallback path after Yaver/local execution fails.
This record as markdown: /tools/io-github-kivanccakmak-yaver/publish-ci-dispatch.md
What publish_ci_dispatch does on Yaver
AI agents invoke publish_ci_dispatch 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 |
|---|---|---|---|
dir | string | — | Project directory. Defaults to the agent work dir. |
target | string | — | Target ID from .yaver/publish.yaml. Defaults to defaultTarget. |
allow_github_fallback | boolean | — | Allow explicit GitHub workflow_dispatch fallback if the target/project permits it. |
Parameters from the server's own tool schema.
Why publish_ci_dispatch is rated High
This tool triggers CI pipeline runs and can dispatch GitHub workflows, which constitutes executing external operations with potentially broad side effects (build, test, deploy pipelines). The fallback to GitHub dispatch means it can trigger remote execution beyond local scope.
From the tool's definition 'Alias of publish_run for CI-oriented clients' and 'GitHub dispatch as the fallback path after Yaver/local execution fails' — triggers CI pipeline execution and dispatches workflows externally
Risk signalsAccepts file system path (dir)
Attacks that exploit this kind of access
The rule that runs publish_ci_dispatch 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 publish_ci_dispatch, this is the rule to start with:
publish_ci_dispatch 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 publish_ci_dispatch call is checked against it from then on.
Questions about publish_ci_dispatch
Alias of publish_run for CI-oriented clients. Use allow_github_fallback=true when you want GitHub dispatch as the fallback path after Yaver/local execution fails. 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.
publish_ci_dispatch accepts 3 parameters: dir, target, allow_github_fallback. 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 publish_ci_dispatch: 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.
publish_ci_dispatch 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 publish_ci_dispatch 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 publish_ci_dispatch. 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.
publish_ci_dispatch 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