This record as markdown: /tools/cmet7-plane-mcp/list-workspaces.md
What list_workspaces does on Plane
AI agents call list_workspaces to retrieve information from Plane without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_workspaces is rated Low
The tool is designed to retrieve a list of workspaces. Despite the empty description, the naming convention 'list_*' strongly indicates a non-destructive data retrieval operation. No modification, deletion, execution, or financial operation is implied.
From the tool's definition Tool name 'list_workspaces' follows the 'list_*' pattern, which the classification rules explicitly identify as a read operation that queries data without side effects.
Attacks that exploit this kind of access
The rule that runs list_workspaces safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Plane, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_workspaces, this is the rule to start with:
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 Plane, apply this rule, and every list_workspaces call is checked against it from then on.
Questions about list_workspaces
list_workspaces is a read tool on the Plane MCP server. It is categorised as a Read tool in the Plane MCP Server, which means it retrieves data without modifying state.
Register the Plane MCP server in PolicyLayer and add a rule for 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 Plane. Nothing to install.
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 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 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.
list_workspaces is provided by the Plane MCP server (cmet7/plane-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Plane, and thousands of servers like it.
This server
Across the catalogue