claude_code_list_workspaces

List workspaces in the organization

SERVERSage MCP SOURCEsagemcp/sagemcp

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/sagemcp-sagemcp/claude-code-list-workspaces.md

WHAT IT DOES

What claude_code_list_workspaces does on Sage MCP

AI agents call claude_code_list_workspaces to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why claude_code_list_workspaces is rated Low

This tool queries and returns a list of existing workspaces. It performs no create, modify, delete, or execute operations. The blast radius of misuse is minimal — an attacker gains visibility into workspace structure but cannot alter data or trigger external actions. Typical read operations carry low severity in security contexts.

From the tool's definition Tool name contains 'list' and description states 'List workspaces in the organization' — a read-only operation that retrieves data without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claude_code_list_workspaces safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claude_code_list_workspaces, this is the rule to start with:

claude_code_list_workspaces Allowed

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

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

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

FAQ

Questions about claude_code_list_workspaces

What does the claude_code_list_workspaces tool do? +

List workspaces in the organization. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on claude_code_list_workspaces? +

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

What risk level is claude_code_list_workspaces? +

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

Can I rate-limit claude_code_list_workspaces? +

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

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

claude_code_list_workspaces is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →claude_git_status on Claude Bridge →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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