update_form_settings

SERVERQuintaDB SOURCEhttps://quintadb.com/mcp

Medium RISK CLASS

Category Write

Parameters 122 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-form-settings.md

WHAT IT DOES

What update_form_settings does on QuintaDB

AI agents use update_form_settings 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
`asc`	boolean	—
`app_id`	string	Yes	Project ID (from list_projects)
`sort_by`	string	—	ID поля сортування
`per_page`	integer	—	Number of records per page (max 100, default 20)
`entity_id`	string	Yes	Form ID (from list_forms or describe_project)
`post_action`	string	—	URL для редіректу після сабміту форми
`send_emails`	boolean	—	Надсилати email-повідомлення при новому записі
`target_page`	string	—	Куди відправити людину ПІСЛЯ надсилання ПУБЛІЧНОЇ форми (віджета). Повний URL. Внутрішнього створення записів співробітником не зачіпає.
`allow_delete`	boolean	—
`turn_off_form`	boolean	—	false removes the limit on the number of records (the form takes records again). true is only needed to switch back on a limit set before.
`allow_database`	boolean	—
`inline_editing`	boolean	—

Parameters from the server's own tool schema.

RISK

Why update_form_settings is rated Medium

An AI agent can call update_form_settings faster than any human can review: one bad instruction and it creates or modifies resources in QuintaDB by the hundred, each call as confident as the last.

Risk signalsHigh parameter count (20 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_form_settings Rate-limited

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

FAQ

Questions about update_form_settings

What does the update_form_settings tool do? +

Form settings. A LIMIT ON HOW MANY RECORDS A FORM TAKES is turn_off_form_after — «close registration at 300 people» is this, and nothing else: never hide the add button or the page for it (that closes the form NOW). The answer says how many records the form holds and whether it is open. Оновити налаштування форми: post_action (redirect URL після сабміту), per_page, sort_by, allow_delete, send_emails, inline_editing, allow_database, lqe_use_only_login та інші. 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_form_settings accept? +

update_form_settings accepts 12 parameters: asc, app_id, sort_by, per_page, entity_id, post_action, send_emails, target_page, allow_delete, turn_off_form, allow_database, inline_editing. Required: app_id, entity_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_form_settings? +

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

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

Can I rate-limit update_form_settings? +

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

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

update_form_settings 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 150 QuintaDB tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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