This record as markdown: /tools/io-github-kivanccakmak-yaver/set-work-dir.md
What set_work_dir does on Yaver
AI agents invoke set_work_dir 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 |
|---|---|---|---|
path | string | Yes | Absolute path to the new working directory |
Parameters from the server's own tool schema.
Why set_work_dir is rated High
Changing the working directory affects the execution context of all subsequent operations. This is an Execute-level action because it modifies the runtime environment of the agent, potentially redirecting file operations, command execution, and deployments to arbitrary paths. Misuse could cause the agent to operate on unintended directories, leading to broad unintended side effects across the system.
From the tool's definition Change the agent's working directory for task execution
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs set_work_dir 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 set_work_dir, this is the rule to start with:
set_work_dir 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 set_work_dir call is checked against it from then on.
Questions about set_work_dir
Change the agent's working directory for task execution. 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.
set_work_dir accepts 1 parameter: path. Required: path. 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 set_work_dir: 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.
set_work_dir 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 set_work_dir 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 set_work_dir. 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.
set_work_dir 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