This record as markdown: /tools/com-quintadb-mcp/add-record-comment.md
What add_record_comment does on QuintaDB
AI agents use add_record_comment 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 |
|---|---|---|---|
body | string | Yes | Текст коментаря |
app_id | string | Yes | Project ID (from list_projects) |
record_id | string | Yes | Record ID (from get_records or search_records) |
Parameters from the server's own tool schema.
Why add_record_comment is rated Medium
This tool creates new data (a comment) that is reversible (comments can be edited or deleted). It modifies the record's state by appending a comment, which is a Write operation. Severity is medium because comments typically affect visibility and notification but do not directly alter critical record data or trigger financial/destructive operations.
From the tool's definition Tool name 'add_record_comment' and description translates to 'Add a comment to a record.' This creates new comment data attached to an existing record.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs add_record_comment 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 add_record_comment, this is the rule to start with:
add_record_comment 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 add_record_comment call is checked against it from then on.
Questions about add_record_comment
Додати коментар до запису. 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.
add_record_comment accepts 3 parameters: body, app_id, record_id. Required: body, 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 add_record_comment: 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.
add_record_comment 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 add_record_comment 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 add_record_comment. 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.
add_record_comment 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