List all workspaces with their filtering rules.
AI agents call list_workspaces to retrieve information from Streamline MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries workspace information without creating, modifying, deleting, or executing any operations. It is a pure read operation that returns existing data structures. The low severity reflects minimal blast radius—unauthorized listing of workspaces could expose organizational structure but does not permit modification or deletion of data.
From the tool's definition Tool name is 'list_workspaces' and description states 'List all workspaces with their filtering rules.' The verb 'list' indicates retrieval of existing data with no modification or execution.
Attacks that exploit this kind of access
List all workspaces with their filtering rules. It is categorised as a Read tool in the Streamline MCP MCP Server, which means it retrieves data without modifying state.
Register the Streamline 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 Streamline MCP. 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 Streamline MCP server (rostehea/streamline-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →