update_field

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 121 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-field.md

WHAT IT DOES

What update_field does on QuintaDB

AI agents use update_field 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
`cols`	integer	—	Кількість колонок для textarea
`desc`	string	—	Опис / підказка під полем
`name`	string	—	Нова назва поля
`rich`	boolean	—	true — rich text editor (для textarea)
`rows`	integer	—	Кількість рядків для textarea
`size`	integer	—	Ширина поля в пікселях
`step`	integer	—	Крок для autoincrement поля
`app_id`	string	Yes	Project ID (from list_projects)
`choices`	array	—	Нові варіанти для select / radio / checkbox (замінює всі поточні)
`default`	string	—	Значення за замовчуванням
`visible`	boolean	—	Чи відображати поле у формі
`field_id`	string	—	ID поля — альтернатива до field_name

Parameters from the server's own tool schema.

RISK

Why update_field is rated Medium

This tool modifies database schema and field properties (name, description, position, options, defaults, constraints) in a way that can be undone. It does not delete data, execute arbitrary code, or cause permanent loss, making it Write rather than Destructive or Execute.

From the tool's definition Tool description states it can 'Змінити/перейменувати поле форми' (change/rename form field) and 'Назву, опис, позицію, опції для select/radio, значення за замовчуванням, обов'язковість, розміри, унікальність' (name, description, position, select/radio…

Risk signalsAccepts URL/endpoint input (validations.URL) · High parameter count (45 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_field Rate-limited

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

FAQ

Questions about update_field

What does the update_field tool do? +

Змінити/перейменувати поле форми (rename field, edit property, update column). Назву, опис, позицію, опції для select/radio, значення за замовчуванням, обов'язковість, розміри, унікальність. Не змінює тип поля. 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_field accept? +

update_field accepts 12 parameters: cols, desc, name, rich, rows, size, step, app_id, choices, default, visible, field_id. Required: app_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_field? +

Register the QuintaDB MCP server in PolicyLayer and add a rule for update_field: 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_field? +

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

Can I rate-limit update_field? +

Yes. Add a rate_limit block to the update_field 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_field completely? +

Set action: deny in the PolicyLayer policy for update_field. 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_field? +

update_field 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_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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