List all workspaces for the authenticated user with content counts
AI agents call list_workspaces to retrieve information from Sidvy MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool simply lists existing workspaces and returns metadata (content counts) for the authenticated user. It performs data retrieval only, making no changes to any workspace or its contents. This is a classic Read operation with minimal blast radius if misused by an AI agent—worst case would be information disclosure of workspace names and sizes the user already has access to.
From the tool's definition Tool name 'list_workspaces' and description 'List all workspaces for the authenticated user with content counts' indicate a retrieval/query operation with no modification or side effects.
Attacks that exploit this kind of access
List all workspaces for the authenticated user with content counts. It is categorised as a Read tool in the Sidvy MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sidvy MCP Server 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 Sidvy MCP Server. 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 Sidvy MCP Server MCP server (martinhjartmyr/sidvy-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 →