workspace_status

Per-app runtime status: on-disk presence, init.md freshness, missing env vars. Read-only.

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-status.md

WHAT IT DOES

What workspace_status does on Yaver

AI agents call workspace_status 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_status is rated Low

This tool queries and reports the runtime status of applications, including file presence and configuration state. The explicit "Read-only" designation confirms it performs no side effects, modifications, or external operations. It is a straightforward diagnostic query tool with minimal security risk, appropriate for development environments where status visibility is needed.

From the tool's definition "Per-app runtime status: on-disk presence, init.md freshness, missing env vars. Read-only." - explicitly marked as read-only and retrieves application state information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

workspace_status Allowed

workspace_status 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_status": {}
  }
}

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

FAQ

Questions about workspace_status

What does the workspace_status tool do? +

Per-app runtime status: on-disk presence, init.md freshness, missing env vars. Read-only. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.

What parameters does workspace_status accept? +

workspace_status 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_status? +

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

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

Can I rate-limit workspace_status? +

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

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

workspace_status 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

claude_git_status on Claude Bridge →get_task_status on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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