List all workspaces accessible to the current user. 工作空间是项目的集合，对应一个研发团队。
AI agents call swanlab_list_workspaces to retrieve information from Swanlab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves a list of workspaces without any side effects, creating data, executing code, or modifying state. It is a straightforward query operation that presents minimal risk even if misused by an AI agent, as it only exposes metadata about accessible workspaces.
From the tool's definition Tool name 'swanlab_list_workspaces' and description explicitly state 'List all workspaces' with no modification capability. Server description confirms 'read-only access'. All sibling tools follow read-only patterns (get_, list_).
Documented attack patterns abuse exactly the kind of access swanlab_list_workspaces gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Swanlab, and nothing reaches the server without passing your rules. This is the rule we recommend for swanlab_list_workspaces:
{
"version": "1",
"default": "deny",
"tools": {
"swanlab_list_workspaces": {}
}
}swanlab_list_workspaces is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all workspaces accessible to the current user. 工作空间是项目的集合，对应一个研发团队。. It is categorised as a Read tool in the Swanlab MCP Server, which means it retrieves data without modifying state.
Register the Swanlab MCP server in PolicyLayer and add a rule for swanlab_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 Swanlab. Nothing to install.
swanlab_list_workspaces 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 swanlab_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.
Set action: deny in the PolicyLayer policy for swanlab_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.
swanlab_list_workspaces is provided by the Swanlab MCP server (nexisato/swanlab-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Swanlab, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Swanlab tools catalogued and risk-classified — across an index of 43,000+ MCP servers.