delete_field
Delete a field (column, property) from a form. Irreversible — all data in this field will be lost. (remove field, drop column)
This record as markdown: /tools/com-quintadb-mcp/delete-field.md
What delete_field does on QuintaDB
AI agents call delete_field 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 | ID проєкту |
field_id | string | — | ID поля |
entity_id | string | Yes | ID форми |
field_name | string | — | Назва поля (пріоритет над field_id) |
Parameters from the server's own tool schema.
Why delete_field is rated Critical
The tool permanently removes a database field/column and destroys all associated data irreversibly. The description explicitly states 'Irreversible — all data in this field will be lost' and references 'drop column', which are hallmark destructive operations. This cannot be undone and affects all records in the database using that field.
From the tool's definition Delete a field (column, property) from a form. Irreversible — all data in this field will be lost. (remove field, drop column)
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs delete_field 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_field, this is the rule to start with:
delete_field 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_field call is checked against it from then on.
Questions about delete_field
Delete a field (column, property) from a form. Irreversible — all data in this field will be lost. (remove field, drop column). 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_field accepts 4 parameters: app_id, field_id, entity_id, field_name. 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_field: 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_field 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_field 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_field. 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_field 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