list_saved_views
Список збережених фільтрів/видів таблиці (SearchResult). Дозволяє агенту дізнатись які views вже існують.
This record as markdown: /tools/com-quintadb-mcp/list-saved-views.md
What list_saved_views does on QuintaDB
AI agents call list_saved_views to retrieve information from QuintaDB without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | — | Опційно — фільтр по формі |
Parameters from the server's own tool schema.
Why list_saved_views is rated Low
This tool retrieves metadata about existing saved views/filters in the database. It performs a query operation that returns information without creating, modifying, or deleting any data. The use case—allowing an agent to discover existing views—is purely informational. No data is written, executed, or destroyed, making it a straightforward Read category tool with low severity.
From the tool's definition Tool name 'list_saved_views' and description indicating it returns a list of existing saved filters/views (SearchResult). The verb 'list' and purpose of discovering what views exist are passive read operations with no side effects.
Attacks that exploit this kind of access
The rule that runs list_saved_views 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 list_saved_views, this is the rule to start with:
list_saved_views is read-only, so it stays allowed. 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 list_saved_views call is checked against it from then on.
Questions about list_saved_views
Список збережених фільтрів/видів таблиці (SearchResult). Дозволяє агенту дізнатись які views вже існують. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_saved_views accepts 2 parameters: app_id, entity_id. Required: app_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 list_saved_views: 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.
list_saved_views is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_saved_views 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 list_saved_views. 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.
list_saved_views 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