search_records
Пошук/фільтрація записів (filter records, find entries, query data). Оператори: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, gt, lt
This record as markdown: /tools/com-quintadb-mcp/search-records.md
What search_records does on QuintaDB
AI agents call search_records 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 | Yes | Form ID (from list_forms or describe_project) |
conditions | array | Yes | Умови пошуку |
Parameters from the server's own tool schema.
Why search_records is rated Low
search_records retrieves or queries data without side effects. The operators provided (comparison, pattern matching, empty checks) are purely query-based and do not create, modify, or delete records. This is a classic Read operation—low severity because it has no blast radius beyond information disclosure.
From the tool's definition Tool description explicitly states 'filter records, find entries, query data' with filtering operators (is, is_not, contains, etc.) that are characteristic of search/retrieval operations with no modification capabilities.
Attacks that exploit this kind of access
The rule that runs search_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 search_records, this is the rule to start with:
search_records 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 search_records call is checked against it from then on.
Questions about search_records
Пошук/фільтрація записів (filter records, find entries, query data). Оператори: is, is_not, contains, not_contains, starts_with, ends_with, is_empty, is_not_empty, gt, lt. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
search_records accepts 3 parameters: app_id, entity_id, conditions. Required: app_id, entity_id, conditions. 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 search_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.
search_records 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 search_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 search_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.
search_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.
This server
Across the catalogue