seed_records
Масовий засів початкових записів у форму. Використовуй для наповнення тестовими/довідниковими даними. Для одного запису краще create_record. Підтримує субформи через subforms.
This record as markdown: /tools/com-quintadb-mcp/seed-records.md
What seed_records does on QuintaDB
AI agents use seed_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 | Yes | Масив записів. Кожен запис — хеш {назва_поля: значення} |
subforms | array | — | Зв'язки субформ [{property_id, dtype_id, subform_dtype_id}]. Рідко потрібно вручну. |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why seed_records is rated Medium
This tool creates or modifies data by bulk-inserting records into a form/database. It is reversible (records can be deleted), so it falls under Write rather than Destructive. The bulk nature and potential to populate large volumes of data elevates severity to medium. Confidence is high due to explicit language about seeding/populating records.
From the tool's definition Tool name 'seed_records' and description explicitly states it performs 'Масовий засів початкових записів' (bulk seeding of initial records) to populate forms with test/reference data.
Attacks that exploit this kind of access
The rule that runs seed_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 seed_records, this is the rule to start with:
seed_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 seed_records call is checked against it from then on.
Questions about seed_records
Масовий засів початкових записів у форму. Використовуй для наповнення тестовими/довідниковими даними. Для одного запису краще create_record. Підтримує субформи через subforms. 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.
seed_records accepts 4 parameters: app_id, records, subforms, entity_id. Required: app_id, records, 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 seed_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.
seed_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 seed_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 seed_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.
seed_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