use_case: - Imports data into a specified table in a workspace. The data to be imported should be provided as a list of dictionaries or as a file path (only local file). If file_path is provided, the format of the file should also be provided (csv or json), else the data parameter will be used. -...
AI agents use import_data 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 |
|---|---|---|---|
data | array | — | The data to be added to the table in json format |
orgId | string | — | The organization ID for the request, if applicable. This is a mandatory parameter for shared workspaces |
tableId | string | Yes | The ID of the table to which data will be added. It is None if the data needs to be added to a new table |
file_path | string | — | The path to a local file containing data to be added to the table |
file_type | string | — | The type of the file being imported ("csv", "json") |
workspaceId | string | Yes | The ID of the workspace containing the table |
Parameters from the server's own tool schema.
This tool creates or modifies data within Zoho Analytics tables in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The import operation can be undone or corrected through subsequent writes or deletes, making it a Write category tool.
From the tool's definition Tool description states it 'Imports data into a specified table' and can be used for 'file upload as well as direct data import into a table.' The action modifies existing tables by adding/updating data.
Risk signalsAccepts file system path (file_path)
Attacks that exploit this kind of access
use_case: - Imports data into a specified table in a workspace. The data to be imported should be provided as a list of dictionaries or as a file path (only local file). If file_path is provided, the format of the file should also be provided (csv or json), else the data parameter will be used. - This can be used for both file upload as well as direct data import into a table. important_notes: - Make sure the the table already exists in the workspace before importing data. - If no table exists, create a table first using the create_table tool before importing the data. - if the file_path is a remote URL, download the file using download_file tool before using this tool. - if the file_path is a remote URL and table does not exist, you can create a new table using the create_table tool, analyse the structure (column structure of the table) of the file using analyse_file_structure tool and then import the data. returns: - A string indicating the result of the import operation. If successful, it returns a success message; otherwise, it returns an error message. 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.
import_data accepts 6 parameters: data, orgId, tableId, file_path, file_type, workspaceId. Required: tableId, 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 import_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.
import_data 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 import_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 import_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.
import_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 →