listWorkspaces

THE RISK

Low Risk

Why listWorkspaces needs a policy

This tool retrieves information about available workspaces without creating, modifying, deleting, executing code, or committing financial obligations. It is a simple listing/enumeration function used for discovery purposes.

From the tool's definition Tool name 'listWorkspaces' and description 'List all currently available IDE workspaces' indicate a query/discovery operation with no side effects.

Documented attack patterns abuse exactly the kind of access listWorkspaces gives an agent:

POLICY

How to control listWorkspaces

PolicyLayer is an MCP gateway — it sits between your AI agents and Patchwork Os, and nothing reaches the server without passing your rules. This is the rule we recommend for listWorkspaces:

policy.json

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

listWorkspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Patchwork Os — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Patchwork Os tools

Execute spawnWorkspace Spawn claude-ide-bridge for a workspace dir. Returns pid/port/authToken once lock appears; Write unwatchFiles Stop watching files for a previously registered watcher by ID. Write createPlan Create .claude-plan.md in workspace root. Markdown with sections and task checklists. Write switchWorkspace Switch the active workspace for this session. Tool descriptions prefixed [ws1]/[ws2] show Read Account sObject API name (e.g. Read getOrchestratorStatus Show the orchestrator bridge status: which IDE instances are connected, their workspaces, Read listBridges List all known IDE bridge instances (healthy and unhealthy) with their ports, workspace pa Read refactorPreview Preview refactoring edits across files without applying. Use getCodeActions first.

All 11 Patchwork Os tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about listWorkspaces

What does the listWorkspaces tool do? +

List all currently available IDE workspaces. Call this to discover which workspaces you can work in before using workspace-specific tools. It is categorised as a Read tool in the Patchwork Os MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on listWorkspaces? +

Register the Patchwork Os MCP server in PolicyLayer and add a rule for listWorkspaces: 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 Patchwork Os. Nothing to install.

What risk level is listWorkspaces? +

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

Can I rate-limit listWorkspaces? +

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

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

listWorkspaces is provided by the Patchwork Os MCP server (oolab-labs/patchwork-os). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Patchwork Os tool call.

Start from Patchwork Os, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →