Create a query table in the specified workspace with the given name and SQL query
AI agents invoke create_query_table 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 ID of the organization to which the workspace belongs. Defaults to config.ORGID if not provided. |
query | string | Yes | The SQL select query to create the query table |
tableName | string | Yes | The name of the query table to create |
workspaceId | string | Yes | The ID of the workspace in which to create the query table |
Parameters from the server's own tool schema.
This tool takes a user-supplied SQL query and executes it within Zoho Analytics to create a query table. Arbitrary SQL execution can read any accessible data, perform joins across sensitive tables, or (depending on the SQL dialect and permissions) trigger destructive operations.
From the tool's definition 'Create a query table ... with the given name and SQL query' — executes arbitrary SQL to define the table
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
Create a query table in the specified workspace with the given name and SQL query. 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.
create_query_table accepts 4 parameters: orgId, query, tableName, workspaceId. Required: query, tableName, 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 create_query_table: 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.
create_query_table 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 create_query_table 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 create_query_table. 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.
create_query_table 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 →