update_record

Оновити існуючий запис. Для rel-полів передай 'rels'. Для subform-полів передай 'subforms'.

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 73 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-quintadb-mcp/update-record.md

WHAT IT DOES

What update_record does on QuintaDB

AI agents use update_record 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
`data`	object	—	Прості поля для оновлення (field_id → value)
`rels`	object	—	Rel-поля: { "Назва rel-поля": "ID запису" } або { "Назва rel-поля": ["id1", "id2"] } для many-to-many
`app_id`	string	Yes	Project ID (from list_projects)
`values`	object	—	Аліас для data — можна використовувати замість data
`subforms`	object	—	Subform-поля: { "field_id subform": { "form_id": "ID субформи", "records": [{"field_id": "значення"}] } }. УВАГА: 'records' — це ОБОВ'ЯЗКОВО масив об'єктів-хеші
`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.

RISK

Why update_record is rated Medium

This tool creates or modifies data reversibly—it updates existing records without deleting or overwriting them irreversibly. The ability to modify related fields (rels) and subforms adds scope but remains within the Write category. Severity is medium because record updates can affect data integrity and dependent queries, but the action is reversible via subsequent updates.

From the tool's definition Tool name 'update_record' and description 'Оновити існуючий запис' (Update existing record) indicates modification of data. Parameters mention 'rels' and 'subforms' suggesting structured data updates.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs update_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 update_record, this is the rule to start with:

update_record Rate-limited

update_record 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_record": {
      "limits": [
        {
          "counter": "update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect QuintaDB, apply this rule, and every update_record call is checked against it from then on.

FAQ

Questions about update_record

What does the update_record tool do? +

Оновити існуючий запис. Для rel-полів передай 'rels'. Для subform-полів передай 'subforms'. 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.

What parameters does update_record accept? +

update_record accepts 7 parameters: data, rels, app_id, values, subforms, 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.

How do I enforce a policy on update_record? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_record? +

update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_record? +

Yes. Add a rate_limit block to the update_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.

How do I block update_record completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_record? +

update_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.

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 116 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →