workspace_layout

Return the runtime-resolved Yaver-managed repository and development-worktree directories. Explicit custom project paths remain supported, and this read-only tool never moves or deletes them.

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-kivanccakmak-yaver/workspace-layout.md

WHAT IT DOES

What workspace_layout does on Yaver

AI agents call workspace_layout 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.

RISK

Why workspace_layout is rated Low

Retrieves workspace directory information without modifying or deleting any data.

From the tool's definition Return runtime-resolved directories. read-only tool never moves or deletes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs workspace_layout 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_layout, this is the rule to start with:

workspace_layout Allowed

workspace_layout is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_layout": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Yaver, apply this rule, and every workspace_layout call is checked against it from then on.

FAQ

Questions about workspace_layout

What does the workspace_layout tool do? +

Return the runtime-resolved Yaver-managed repository and development-worktree directories. Explicit custom project paths remain supported, and this read-only tool never moves or deletes them. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on workspace_layout? +

Register the Yaver MCP server in PolicyLayer and add a rule for workspace_layout: 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.

What risk level is workspace_layout? +

workspace_layout is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit workspace_layout? +

Yes. Add a rate_limit block to the workspace_layout 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.

How do I block workspace_layout completely? +

Set action: deny in the PolicyLayer policy for workspace_layout. 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.

What MCP server provides workspace_layout? +

workspace_layout 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.

KEEP EXPLORING

More on Yaver, and thousands of servers like it.

This server

All 678 Yaver tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →