use case: - Executes a SQL query on the specified workspace and returns the top 20 rows as results. - This can be used to retrieve data from Zoho Analytics using custom SQL queries. - Use this when user asks for any queries from the data in the workspace. - Use this to gather insights from the da...
AI agents invoke query_data to trigger actions in Zoho Analytics. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | — | The organization ID for the request, if applicable. This is a mandatory parameter for shared workspaces |
sql_query | string | Yes | The SQL query to be executed |
workspaceId | string | Yes | The ID of the workspace where the query will be executed |
Parameters from the server's own tool schema.
Although the description advises SELECT-only queries, the tool executes arbitrary SQL against the workspace. There is no enforced restriction preventing destructive SQL (DROP, DELETE, UPDATE) from being passed. The word 'Executes a SQL query' places this in the Execute category rather than Read.
From the tool's definition Executes a SQL query on the specified workspace and returns the top 20 rows as results. Always try to provide a mysql compatible sql select query alone.
Attacks that exploit this kind of access
use case: - Executes a SQL query on the specified workspace and returns the top 20 rows as results. - This can be used to retrieve data from Zoho Analytics using custom SQL queries. - Use this when user asks for any queries from the data in the workspace. - Use this to gather insights from the data in the workspace and answer user queries. - Can be used to answer natural language queries by analysing the result of the SQL query. important_notes: - Always try to provide a mysql compatible sql select query alone. - Try to optimize the query to return only the required data and minimize the amount of data returned. - If table or column names contain spaces or special characters, enclose them in double quotes (e.g., "Column Name"). - Do not use more than one level of nested sub-queries. - Instead of doing n queries, try to combine them into a single query using joins or unions or sub-queries, while ensuring the query remains efficient. returns: - Result of the SQL query in a comma-separated (list of list) format of the top 20 rows alone, the first row contains the column names. - If an error occurs, returns an error message. It is categorised as a Execute tool in the Zoho Analytics MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
query_data accepts 3 parameters: orgId, sql_query, workspaceId. Required: sql_query, 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 query_data: 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.
query_data is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the query_data 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 query_data. 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.
query_data 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 →