This record as markdown: /tools/com-quintadb-mcp/delete-record.md
What delete_record does on QuintaDB
AI agents call delete_record 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) |
record_id | string | Yes | Record ID (from get_records or search_records) |
Parameters from the server's own tool schema.
Why delete_record is rated Critical
This tool permanently deletes database records without the ability to undo the operation. While the blast radius depends on what record is targeted, deletion of records is by definition irreversible and falls into the Destructive category, which is more severe than Write (which covers reversible modifications).
From the tool's definition Tool name is 'delete_record' and description translates from Ukrainian as 'Delete record'. The action irreversibly removes data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_record, this is the rule to start with:
delete_record 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_record call is checked against it from then on.
Questions about delete_record
Видалити запис. 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_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 delete_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.
delete_record 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_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 delete_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.
delete_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.
Across the catalogue