bulk_update_records

Масово оновити поле(я) у багатьох записах одразу. Замість 'постав статус Оброблено всім замовленням за сьогодні' через N викликів update_record. Записи можна вибрати: за списком ID, за фільтром (поле=значення), за звітом або всі записи форми. Підтримує action rules — тригери спрацюють як при звич...

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 63 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What bulk_update_records does on QuintaDB

AI agents use bulk_update_records 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
`app_id`	string	Yes	Project ID (from list_projects)
`filter`	object	—	Фільтр по одному полю: {field: "Назва поля", value: "значення"}. Наприклад: {field: "Статус", value: "Новий"}
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`report_id`	string	—	ID звіту/фільтру — оновить тільки записи що входять в цей звіт
`record_ids`	array	—	Конкретні ID записів для оновлення. Якщо не вказано — використовується filter або report_id або всі записи.
`fields_to_set`	object	Yes	Поля для оновлення: {"Назва поля" або field_id: "нове значення"}. Наприклад: {"Статус": "Оброблено", "Пріоритет": "Низький"}

Parameters from the server's own tool schema.

RISK

Why bulk_update_records is rated Medium

This tool creates or modifies data reversibly across many records. It is Write, not Destructive, because bulk updates do not irreversibly delete data. However, the blast radius is high because a single call can modify many records simultaneously across a database (potentially all records in a form), and automation triggers add unpredictable side effects. An AI agent misuse could corrupt significant data sets.

From the tool's definition bulk_update_records: 'Масово оновити поле(я) у багатьох записах одразу' (bulk update fields in many records at once) — modifies data across multiple records; 'Записи можна вибрати: за списком ID, за фільтром...за звітом або всі записи форми' (records can be…

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bulk_update_records Rate-limited

bulk_update_records 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": {
    "bulk_update_records": {
      "limits": [
        {
          "counter": "bulk_update_records_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 bulk_update_records call is checked against it from then on.

FAQ

Questions about bulk_update_records

What does the bulk_update_records tool do? +

What parameters does bulk_update_records accept? +

bulk_update_records accepts 6 parameters: app_id, filter, entity_id, report_id, record_ids, fields_to_set. Required: app_id, entity_id, fields_to_set. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bulk_update_records? +

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

What risk level is bulk_update_records? +

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

Can I rate-limit bulk_update_records? +

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

How do I block bulk_update_records completely? +

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

What MCP server provides bulk_update_records? +

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

KEEP EXPLORING

More on QuintaDB, and thousands of servers like it.

This server

All 116 QuintaDB tools →

Across the catalogue

sms_send_bulk on Twilio SMS MCP Server →aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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