update_form_settings
Оновити налаштування форми: post_action (redirect URL після сабміту), per_page, sort_by, allow_delete, send_emails, inline_editing, allow_database, lqe_use_only_login та інші.
This record as markdown: /tools/com-quintadb-mcp/update-form-settings.md
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-повідомлення при новому записі |
allow_delete | boolean | — | |
allow_database | boolean | — | |
inline_editing | boolean | — | |
dtype_added_text | string | — | Текст після успішного сабміту форми |
lqe_use_only_login | boolean | — |
Parameters from the server's own tool schema.
Why update_form_settings is rated Medium
This tool modifies form configuration settings reversibly. While it doesn't create or delete records, it alters system behavior—including email triggers (send_emails), deletion permissions (allow_delete), and redirect behavior (post_action)—which could misdirect users, enable unintended deletions, or trigger unwanted notifications if misused by an AI agent.
From the tool's definition Tool updates form settings including post_action, per_page, sort_by, allow_delete, send_emails, inline_editing, allow_database, and lqe_use_only_login. These are configuration modifications that create or alter form behavior and permissions.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
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 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 update_form_settings call is checked against it from then on.
Questions about update_form_settings
Оновити налаштування форми: 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.
update_form_settings accepts 12 parameters: asc, app_id, sort_by, per_page, entity_id, post_action, send_emails, allow_delete, allow_database, inline_editing, dtype_added_text, lqe_use_only_login. Required: app_id, entity_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 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.
update_form_settings 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 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.
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.
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.
More on QuintaDB, and thousands of servers like it.
This server
Across the catalogue