workspace_scaffold
Detect apps in the current directory and return a starter yaver.workspace.yaml. Does NOT write the file — caller decides (keeps the tool side-effect-free for agents that want to review first).
This record as markdown: /tools/io-github-kivanccakmak-yaver/workspace-scaffold.md
What workspace_scaffold does on Yaver
AI agents call workspace_scaffold 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 |
|---|---|---|---|
root | string | — |
Parameters from the server's own tool schema.
Why workspace_scaffold is rated Low
The tool explicitly states it does not write any files and is intentionally side-effect-free. It only detects and returns configuration content for review, making it a pure read/query operation with minimal blast radius.
From the tool's definition 'Detect apps in the current directory and return a starter yaver.workspace.yaml. Does NOT write the file — caller decides (keeps the tool side-effect-free for agents that want to review first).'
Attacks that exploit this kind of access
The rule that runs workspace_scaffold 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 workspace_scaffold, this is the rule to start with:
workspace_scaffold 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 workspace_scaffold call is checked against it from then on.
Questions about workspace_scaffold
Detect apps in the current directory and return a starter yaver.workspace.yaml. Does NOT write the file — caller decides (keeps the tool side-effect-free for agents that want to review first). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
workspace_scaffold accepts 1 parameter: root. 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 workspace_scaffold: 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.
workspace_scaffold 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 workspace_scaffold 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 workspace_scaffold. 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.
workspace_scaffold 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