duplicate_record
Створити копію запису з усіма значеннями полів (асинхронно через CloneRecordJob).
This record as markdown: /tools/com-quintadb-mcp/duplicate-record.md
What duplicate_record does on QuintaDB
AI agents use duplicate_record 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) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
record_id | string | Yes | Record ID (from get_records or search_records) |
Parameters from the server's own tool schema.
Why duplicate_record is rated Medium
The tool duplicates an existing record, resulting in a new record being added to the database. This is a reversible write operation (the duplicate can be deleted). It does not delete, destroy, or execute arbitrary code; it only creates new data.
From the tool's definition Tool creates a copy of a record with all field values (via CloneRecordJob), which is a write operation that modifies the database by adding new data.
Attacks that exploit this kind of access
The rule that runs duplicate_record 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 duplicate_record, this is the rule to start with:
duplicate_record 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 duplicate_record call is checked against it from then on.
Questions about duplicate_record
Створити копію запису з усіма значеннями полів (асинхронно через CloneRecordJob). 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.
duplicate_record accepts 3 parameters: app_id, entity_id, record_id. Required: app_id, entity_id, record_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 duplicate_record: 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.
duplicate_record 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 duplicate_record 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 duplicate_record. 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.
duplicate_record 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