workspace_web_apps
Return workspace apps whose stack maps to a web surface (nextjs, vite, flutter, react-native-expo). Used by the Web Reload dashboard tab to populate its app picker.
This record as markdown: /tools/io-github-kivanccakmak-yaver/workspace-web-apps.md
What workspace_web_apps does on Yaver
AI agents call workspace_web_apps 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 |
|---|---|---|---|
kind | string | — | Comma-separated kinds to keep (web,hybrid,mobile). Defaults to web,hybrid. |
root | string | — | Repo root. Defaults to agent CWD. |
Parameters from the server's own tool schema.
Why workspace_web_apps is rated Low
This tool retrieves and filters a list of workspace applications based on their technology stack. It performs a query operation to populate UI elements, with no capability to create, modify, delete, or execute code. The blast radius of misuse is minimal—an attacker could at most learn which web-based apps exist in a workspace, which is low-sensitivity information in a local development context.
From the tool's definition Tool name includes 'Return', and description states 'Return workspace apps whose stack maps to a web surface' and 'Used by the Web Reload dashboard tab to populate its app picker.' The verb 'Return' and use case (populating a picker) indicate data retrieval…
Attacks that exploit this kind of access
The rule that runs workspace_web_apps 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_web_apps, this is the rule to start with:
workspace_web_apps 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_web_apps call is checked against it from then on.
Questions about workspace_web_apps
Return workspace apps whose stack maps to a web surface (nextjs, vite, flutter, react-native-expo). Used by the Web Reload dashboard tab to populate its app picker. It is categorised as a Read tool in the Yaver MCP Server, which means it retrieves data without modifying state.
workspace_web_apps accepts 2 parameters: kind, 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_web_apps: 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_web_apps 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_web_apps 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_web_apps. 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_web_apps 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