<use_case> 1) Fetches the list of workspaces in the user's organization. 2) Used in the scenario where the user needs to select a workspace for further operations. </use_case> <important_notes> 1) Try to avoid setting include_shared_workspaces to True unless you specifically need to see shared wo...
AI agents call get_workspaces_list to retrieve information from Zoho Analytics without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
contains_str | string | — | Optional string to filter workspaces with a contains criteria |
include_shared_workspaces | boolean | Yes | If True, includes shared workspaces in the list |
Parameters from the server's own tool schema.
The tool retrieves and lists existing workspaces for selection purposes, matching the Read category definition: 'retrieves or queries data; no side effects (search, list, get, fetch).' The severity is low because listing workspaces is a non-destructive query with minimal blast radius if misused.
From the tool's definition Tool name is "get_workspaces_list" and description states it "Fetches the list of workspaces in the user's organization." This is a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
<use_case> 1) Fetches the list of workspaces in the user's organization. 2) Used in the scenario where the user needs to select a workspace for further operations. </use_case> <important_notes> 1) Try to avoid setting include_shared_workspaces to True unless you specifically need to see shared workspaces. 2) If you don't find a workspace from the owned workspaces, try setting include_shared_workspaces to True to see if the workspace is shared with you. </important_notes> <returns> A list of dictionaries, each representing a workspace with its details. If an error occurs, returns an error message. </returns>. It is categorised as a Read tool in the Zoho Analytics MCP Server, which means it retrieves data without modifying state.
get_workspaces_list accepts 2 parameters: contains_str, include_shared_workspaces. Required: include_shared_workspaces. The full parameter table on this page comes from the server's own tool schema.
Register the Zoho Analytics MCP server in PolicyLayer and add a rule for get_workspaces_list: 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 Zoho Analytics. Nothing to install.
get_workspaces_list 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 get_workspaces_list 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 get_workspaces_list. 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.
get_workspaces_list is provided by the Zoho Analytics MCP server (zoho-analytics-mcp-server). 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 →