This record as markdown: /tools/com-quintadb-mcp/list-record-comments.md
What list_record_comments does on QuintaDB
AI agents call list_record_comments 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) |
record_id | string | Yes | ID запису (dtype) |
Parameters from the server's own tool schema.
Why list_record_comments is rated Low
This tool retrieves existing comments associated with a record. It performs a query operation without creating, modifying, deleting, or executing anything. The blast radius of misuse is minimal—an agent could read comments it shouldn't access, but cannot alter or delete data. This is a standard Read category operation.
From the tool's definition Tool name 'list_record_comments' and description 'Отримати коментарі до запису' (Ukrainian: 'Get comments to a record') both indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs list_record_comments 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_record_comments, this is the rule to start with:
list_record_comments 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_record_comments call is checked against it from then on.
Questions about list_record_comments
Отримати коментарі до запису. It is categorised as a Read tool in the QuintaDB MCP Server, which means it retrieves data without modifying state.
list_record_comments accepts 2 parameters: app_id, record_id. Required: app_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 list_record_comments: 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_record_comments 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_record_comments 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_record_comments. 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_record_comments 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