workspace_list

Return apps declared in yaver.workspace.yaml, ordered by dependency (leaf-first).

SERVERYaver SOURCEyaver-cli

Low RISK CLASS

Category Read

Parameters 10 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-list.md

WHAT IT DOES

What workspace_list does on Yaver

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

RISK

Why workspace_list is rated Low

This tool queries and returns configuration data from a local workspace file. It has no side effects—it only lists applications in dependency order. The operation is read-only, making it a Read category tool with low severity since disclosure of workspace configuration has minimal blast radius in a local development context.

From the tool's definition Tool name 'workspace_list' and description 'Return apps declared in yaver.workspace.yaml' indicate a retrieval operation with no modification, deletion, or execution of external systems.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

workspace_list Allowed

workspace_list 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_list": {}
  }
}

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_list call is checked against it from then on.

FAQ

Questions about workspace_list

What does the workspace_list tool do? +

Return apps declared in yaver.workspace.yaml, ordered by dependency (leaf-first). It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does workspace_list accept? +

workspace_list accepts 1 parameter: root. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on workspace_list? +

Register the Yaver MCP server in PolicyLayer and add a rule for workspace_list: 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_list? +

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

Can I rate-limit workspace_list? +

Yes. Add a rate_limit block to the workspace_list 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_list completely? +

Set action: deny in the PolicyLayer policy for workspace_list. 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_list? +

workspace_list 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 645 Yaver tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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