delete_few_records
Видалити декілька записів одним запитом
This record as markdown: /tools/com-quintadb-mcp/delete-few-records.md
What delete_few_records does on QuintaDB
AI agents call delete_few_records 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_ids | array | Yes | Масив ID записів для видалення |
Parameters from the server's own tool schema.
Why delete_few_records is rated Critical
Deletion of records is a destructive operation that cannot be undone and permanently removes data from the database. This ranks above Write/Execute because the action is irreversible. Even though it operates on 'few' records rather than all records, the core operation remains destructive.
From the tool's definition Tool name is 'delete_few_records' and description translates to 'Delete several records in one request'. The verb 'delete' combined with 'records' directly indicates irreversible removal of data.
Attacks that exploit this kind of access
The rule that runs delete_few_records 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_few_records, this is the rule to start with:
delete_few_records 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_few_records call is checked against it from then on.
Questions about delete_few_records
Видалити декілька записів одним запитом. 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_few_records accepts 3 parameters: app_id, entity_id, record_ids. Required: app_id, entity_id, record_ids. 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_few_records: 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_few_records 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_few_records 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_few_records. 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_few_records 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