publish_run
Run a publish target from .yaver/publish.yaml. Local/self-hosted execution is primary; GitHub fallback is used only when allowed and requested.
This record as markdown: /tools/io-github-kivanccakmak-yaver/publish-run.md
What publish_run does on Yaver
AI agents invoke publish_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 |
|---|---|---|---|
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_run is rated High
This tool executes a publish pipeline (build, deploy, or release steps) from a configuration file. Publish targets typically involve running scripts, building artifacts, and deploying to environments. This is Execute-level at minimum; since it may deploy code to production environments, the blast radius is high.
From the tool's definition 'Run a publish target' and 'Local/self-hosted execution is primary; GitHub fallback is used only when allowed and requested' — triggers external build/publish operations defined in a YAML config
Risk signalsAccepts file system path (dir)
Attacks that exploit this kind of access
The rule that runs publish_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 publish_run, this is the rule to start with:
publish_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 publish_run call is checked against it from then on.
Questions about publish_run
Run a publish target from .yaver/publish.yaml. Local/self-hosted execution is primary; GitHub fallback is used only when allowed and requested. 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_run 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_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.
publish_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 publish_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 publish_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.
publish_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