This record as markdown: /tools/com-quintadb-mcp/delete-saved-view.md
What delete_saved_view does on QuintaDB
AI agents call delete_saved_view 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) |
view_id | integer | Yes | Saved view ID (from list_saved_views) |
Parameters from the server's own tool schema.
Why delete_saved_view is rated Critical
This tool permanently removes a saved view configuration from the database. Deletion is irreversible and cannot be undone through normal means. While the blast radius is limited to a single view object (not data records themselves), it still qualifies as Destructive rather than Write because the action cannot be reversed and represents loss of a configured artifact.
From the tool's definition Tool name 'delete_saved_view' combined with description 'Видалити збережений фільтр (view)' (Ukrainian: 'Delete saved filter (view)') explicitly indicates irreversible deletion of a saved view/filter object.
Attacks that exploit this kind of access
The rule that runs delete_saved_view 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_saved_view, this is the rule to start with:
delete_saved_view 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_saved_view call is checked against it from then on.
Questions about delete_saved_view
Видалити збережений фільтр (view). 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_saved_view accepts 2 parameters: app_id, view_id. Required: app_id, view_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_saved_view: 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_saved_view 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_saved_view 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_saved_view. 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_saved_view 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