use_case: 1) Searches for views in a workspace using either contains string name matching or natural language query via Retrieval-Augmented Generation (RAG). 2) Use this when you need to find specific views or views relevant to a question. important_notes: - If view_contains_str is provided, perf...
AI agents call search_views 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 |
|---|---|---|---|
orgId | object | — | |
workspaceId | string | Yes | |
view_contains_str | string | — | |
allowedViewTypesIds | array | — | |
natural_language_query | string | — |
Parameters from the server's own tool schema.
search_views is a pure query/search function that retrieves or lists data (views matching search criteria) without any side effects. It uses string matching or RAG-based semantic search to find views but does not create, modify, delete, or execute any operations. This clearly fits the Read category with low severity since misuse would only expose information about available views in a workspace.
From the tool's definition Tool performs search and retrieval operations on views: 'Searches for views in a workspace using either contains string name matching or natural language query'. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
use_case: 1) Searches for views in a workspace using either contains string name matching or natural language query via Retrieval-Augmented Generation (RAG). 2) Use this when you need to find specific views or views relevant to a question. important_notes: - If view_contains_str is provided, performs simple string matching on view names. - If view_contains_str is None and natural_language_query is provided, performs intelligent RAG-based search using natural language. - If both view_contains_str and natural_language_query are provided, view_contains_str takes precedence and RAG search is not performed. - If both are None, returns views without filtering (may error if too many). - If not specified explicitly, uses [0, 6] as default value for allowedViewTypesIds (Table and Query Table). arguments: - workspaceId: The ID of the workspace to search in. - natural_language_query: Natural language query for intelligent search. Ignored if view_contains_str is provided. - view_contains_str: String to filter views by name matching. Takes precedence over natural_language_query. - allowedViewTypesIds: Optional array of view type IDs to filter results. It should be an array of integers. Different types of views available in zoho analytics are: (view type_id, view_type_name) 0 - Table: A standard table 2 - Chart: A graphical representation of data 3 - Pivot Table: A table that summarizes data in a multidimensional format 4 - Summary View: A view that provides a simple tabular summary of your data with aggregate functions applied 6 - Query Table: A derived table created from a custom SQL query 7 - Dashboard: A collection of visualizations and reports - orgId: Organization ID. Defaults to config value if not provided. returns: - A JSON stringified array of views matching the criteria or an error message string. It is categorised as a Read tool in the Zoho Analytics MCP Server, which means it retrieves data without modifying state.
search_views accepts 5 parameters: orgId, workspaceId, view_contains_str, allowedViewTypesIds, natural_language_query. Required: workspaceId. 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 search_views: 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.
search_views 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 search_views 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 search_views. 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.
search_views 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 →