mcp__automation__list_workspaces
查询可作为定时任务创建目标的工作区，仅返回 ID、名称、slug、是否当前工作区和项目根状态，不读取文件内容。跨工作区创建前先查询并用精确 ID 选择；重名时向用户确认。managed 表示托管项目；missing/not_directory/unavailable 表示本地项目根不可用。
This record as markdown: /tools/dutydeck/mcp--automation--list-workspaces.md
What mcp__automation__list_workspaces does on DutyDeck
AI agents call mcp__automation__list_workspaces to retrieve information from DutyDeck without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp__automation__list_workspaces is rated Low
Even though mcp__automation__list_workspaces only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs mcp__automation__list_workspaces safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DutyDeck, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp__automation__list_workspaces, this is the rule to start with:
mcp__automation__list_workspaces 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 DutyDeck, apply this rule, and every mcp__automation__list_workspaces call is checked against it from then on.
Questions about mcp__automation__list_workspaces
查询可作为定时任务创建目标的工作区，仅返回 ID、名称、slug、是否当前工作区和项目根状态，不读取文件内容。跨工作区创建前先查询并用精确 ID 选择；重名时向用户确认。managed 表示托管项目；missing/not_directory/unavailable 表示本地项目根不可用。. It is categorised as a Read tool in the DutyDeck MCP Server, which means it retrieves data without modifying state.
Register the DutyDeck MCP server in PolicyLayer and add a rule for mcp__automation__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 DutyDeck. Nothing to install.
mcp__automation__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 mcp__automation__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 mcp__automation__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.
mcp__automation__list_workspaces is provided by the DutyDeck MCP server (taokoplay/DutyDeck). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DutyDeck, and thousands of servers like it.
This server
Across the catalogue