create_saved_view
Створити збережений фільтр (view) для таблиці з критеріями фільтрації та сортуванням.
This record as markdown: /tools/com-quintadb-mcp/create-saved-view.md
What create_saved_view does on QuintaDB
AI agents use create_saved_view to create or update resources in QuintaDB, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your QuintaDB environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Display name |
app_id | string | Yes | Project ID (from list_projects) |
filters | array | — | Масив умов фільтрації |
sort_by | string | — | field_name або field_id для сортування |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
order_asc | boolean | — | true=ASC (default), false=DESC |
Parameters from the server's own tool schema.
Why create_saved_view is rated Medium
This tool creates a new saved view configuration, which is reversible data modification (Write category). It does not retrieve data, execute code, delete anything, or involve financial operations. The severity is low because saved views are UI/configuration changes that do not affect underlying data and can be easily modified or deleted.
From the tool's definition create_saved_view creates a saved filter/view for a table with filtering criteria and sorting. The tool name and description indicate it creates and stores a new configuration object (a view definition) that modifies how data is presented.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs create_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 create_saved_view, this is the rule to start with:
create_saved_view stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every create_saved_view call is checked against it from then on.
Questions about create_saved_view
Створити збережений фільтр (view) для таблиці з критеріями фільтрації та сортуванням. It is categorised as a Write tool in the QuintaDB MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_saved_view accepts 6 parameters: name, app_id, filters, sort_by, entity_id, order_asc. Required: name, 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 create_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.
create_saved_view is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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 create_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.
create_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.
This server
Across the catalogue