delete_records_by_filter
Масове видалення записів за фільтром, переліком ID або всіх записів форми. Незворотна операція.
This record as markdown: /tools/com-quintadb-mcp/delete-records-by-filter.md
What delete_records_by_filter does on QuintaDB
AI agents call delete_records_by_filter 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 |
|---|---|---|---|
all | boolean | — | true — видалити всі записи форми (небезпечно!) |
limit | integer | — | Максимальна кількість записів для видалення (захист від помилок) |
app_id | string | Yes | ID проєкту |
filter | object | — | Фільтр по значенню поля: {field: 'Статус', value: 'Архів'} |
entity_id | string | Yes | ID форми |
record_ids | array | — | Конкретні ID записів для видалення |
Parameters from the server's own tool schema.
Why delete_records_by_filter is rated Critical
This tool irreversibly deletes data at scale with no undo mechanism. It matches the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The blast radius is critical because an AI agent misusing filter logic could delete entire datasets unintentionally, and the operation cannot be recovered.
From the tool's definition Tool description states 'Масове видалення записів' (bulk deletion of records) and explicitly notes 'Незворотна операція' (irreversible operation). The tool deletes records by filter, ID list, or all form records.
Attacks that exploit this kind of access
The rule that runs delete_records_by_filter 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_records_by_filter, this is the rule to start with:
delete_records_by_filter 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_records_by_filter call is checked against it from then on.
Questions about delete_records_by_filter
Масове видалення записів за фільтром, переліком ID або всіх записів форми. Незворотна операція. 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_records_by_filter accepts 6 parameters: all, limit, app_id, filter, entity_id, record_ids. 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_records_by_filter: 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_records_by_filter 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_records_by_filter 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_records_by_filter. 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_records_by_filter 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