import_records
Масово імпортувати записи з CSV або масиву об'єктів. Для масиву 'records' ОБОВ'ЯЗКОВО використовуй ID полів як ключі.
This record as markdown: /tools/com-quintadb-mcp/import-records.md
What import_records does on QuintaDB
AI agents use import_records to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
records | array | — | Масив об'єктів де ключі — ID полів форми (не назви!). Альтернатива до csv_text. Приклад: [{"dcTrJdP1bppyk3vCkKvCoN": "Іван"}] |
csv_text | string | — | CSV-текст з заголовками в першому рядку. Підтримує коми і крапку з комою як роздільник. Приклад: "Ім'я,Email,Статус\nІван,ivan@ex.com,Новий" |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why import_records is rated Medium
This tool creates or modifies data (adds records to a database) without permanently destroying information. While bulk operations carry higher risk due to scale (potentially affecting many records at once), the operation is reversible—imported records can be deleted or corrected.
From the tool's definition Tool description states 'Масово імпортувати записи' (bulk import records) from CSV or object arrays. The core function is creating/adding multiple records to the database in bulk, which is a write operation that modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs import_records safely
PolicyLayer is an MCP gateway: it sits between your AI agents and QuintaDB, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For import_records, this is the rule to start with:
import_records stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every import_records call is checked against it from then on.
Questions about import_records
Масово імпортувати записи з CSV або масиву об'єктів. Для масиву 'records' ОБОВ'ЯЗКОВО використовуй ID полів як ключі. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
import_records accepts 4 parameters: app_id, records, csv_text, entity_id. Required: app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.
Register the QuintaDB MCP server in PolicyLayer and add a rule for import_records: 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 QuintaDB. Nothing to install.
import_records 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_records 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_records. 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_records is provided by the QuintaDB MCP server (https://quintadb.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue