duplicate_form
Скопіювати форму разом з полями, налаштуваннями і записами. Асинхронна операція (~10 сек).
This record as markdown: /tools/com-quintadb-mcp/duplicate-form.md
What duplicate_form does on QuintaDB
AI agents use duplicate_form 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) |
Parameters from the server's own tool schema.
Why duplicate_form is rated Medium
Duplication creates new data objects (form copy with associated fields, settings, and records) but does not modify or delete originals. This is a reversible write operation. Severity is medium because duplicating an entire form with all its records could create unintended data proliferation or confusion if triggered maliciously, but the operation itself is not destructive and can be undone by deleting the duplicate.
From the tool's definition Tool name 'duplicate_form' and description indicating it copies/duplicates a form with fields, settings, and records. The description states 'Скопіювати форму разом з полями, налаштуваннями і записами' (Copy form together with fields, settings and records).
Attacks that exploit this kind of access
The rule that runs duplicate_form 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_form, this is the rule to start with:
duplicate_form 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_form call is checked against it from then on.
Questions about duplicate_form
Скопіювати форму разом з полями, налаштуваннями і записами. Асинхронна операція (~10 сек). 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_form accepts 2 parameters: app_id, 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 duplicate_form: 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_form 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_form 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_form. 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_form 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