delete_form
Видалити форму та всі її записи. Незворотна операція. Не можна видалити єдину форму.
This record as markdown: /tools/com-quintadb-mcp/delete-form.md
What delete_form does on QuintaDB
AI agents call delete_form to permanently remove resources in QuintaDB, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| 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 delete_form is rated Critical
This tool permanently deletes a form and all associated records without the ability to undo. This is irreversible data destruction affecting potentially large datasets, making it Destructive rather than Write. The high severity reflects the blast radius of accidental invocation by an AI agent, which could result in complete loss of forms and their data.
From the tool's definition Tool name is 'delete_form'. Description states 'Видалити форму та всі її записи' (delete form and all its records) and 'Незворотна операція' (irreversible operation).
Attacks that exploit this kind of access
The rule that runs delete_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 delete_form, this is the rule to start with:
delete_form is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every delete_form call is checked against it from then on.
Questions about delete_form
Видалити форму та всі її записи. Незворотна операція. Не можна видалити єдину форму. It is categorised as a Destructive tool in the QuintaDB MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_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 delete_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.
delete_form is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue