Create a new table in the given workspace with the given name
AI agents use create_table to create or update resources in Zoho Analytics — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zoho Analytics environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
orgId | string | — | The ID of the organization to which the workspace belongs. Defaults to config.ORGID if not provided. |
tableName | string | Yes | The name of the table to create |
columns_arr | array | Yes | A list of column definitions for the table |
workspaceId | string | Yes | The ID of the workspace in which to create the table |
Parameters from the server's own tool schema.
The tool creates a new table, which is a reversible write operation. It modifies the workspace by adding a new data container but does not execute arbitrary code, delete data irreversibly, or move funds. The medium severity reflects that unauthorized table creation could disrupt analytics workflows and consume storage, but the effect is not catastrophic or irreversible at the system level.
From the tool's definition Tool description states 'Create a new table in the given workspace with the given name' — this creates new data structures within Zoho Analytics.
Attacks that exploit this kind of access
Create a new table in the given workspace with the given name. It is categorised as a Write tool in the Zoho Analytics MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_table accepts 4 parameters: orgId, tableName, columns_arr, workspaceId. Required: tableName, columns_arr, 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_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_table is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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_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_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 →