publish_config_get
Load a project's Yaver publish config (.yaver/publish.yaml). Returns the existing config or a scaffold preview if none exists yet.
This record as markdown: /tools/io-github-kivanccakmak-yaver/publish-config-get.md
What publish_config_get does on Yaver
AI agents call publish_config_get 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 |
|---|---|---|---|
dir | string | — | Project directory. Defaults to the agent work dir. |
Parameters from the server's own tool schema.
Why publish_config_get is rated Low
This tool only reads and returns configuration data from a YAML file. It has no side effects — it does not modify, create, or delete anything. The scaffold preview is returned as output, not written to disk. Pure read operation with minimal blast radius.
From the tool's definition 'Load a project's Yaver publish config' and 'Returns the existing config or a scaffold preview if none exists yet'
Risk signalsAccepts file system path (dir)
Attacks that exploit this kind of access
The rule that runs publish_config_get 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_config_get, this is the rule to start with:
publish_config_get 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 publish_config_get call is checked against it from then on.
Questions about publish_config_get
Load a project's Yaver publish config (.yaver/publish.yaml). Returns the existing config or a scaffold preview if none exists yet. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
publish_config_get accepts 1 parameter: dir. 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_config_get: 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_config_get 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 publish_config_get 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_config_get. 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_config_get 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