This record as markdown: /tools/com-quintadb-mcp/get-record.md
What get_record does on QuintaDB
AI agents call get_record 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) |
record_id | string | Yes | Record ID (from get_records or search_records) |
Parameters from the server's own tool schema.
Why get_record is rated Low
This tool retrieves data without side effects. It queries an existing record by ID, which is a read-only operation. The blast radius is minimal—unauthorized access could expose sensitive data within that record, but the operation itself is non-destructive and reversible. Severity is low because it is a single-record read operation.
From the tool's definition Tool name 'get_record' and description 'Отримати один запис по ID' (Ukrainian: 'Get one record by ID') indicate retrieval of a single data record by identifier with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs get_record 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 get_record, this is the rule to start with:
get_record 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 get_record call is checked against it from then on.
Questions about get_record
Отримати один запис по ID. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
get_record accepts 3 parameters: app_id, entity_id, record_id. Required: app_id, entity_id, record_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 get_record: 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.
get_record 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 get_record 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 get_record. 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.
get_record 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