update_form
Змінити назву, опис або налаштування форми.
This record as markdown: /tools/com-quintadb-mcp/update-form.md
What update_form does on QuintaDB
AI agents use update_form 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 |
|---|---|---|---|
desc | string | — | Опис форми |
name | string | — | Нова назва форми |
app_id | string | Yes | Project ID (from list_projects) |
per_page | integer | — | Кількість записів на сторінці |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why update_form is rated Medium
This tool modifies form properties (name, description, settings) but does not delete data or execute arbitrary code. Changes to form configuration are reversible through subsequent updates. The impact is limited to form structure/metadata rather than underlying records, making it a Write operation with medium severity due to potential for misconfiguration affecting users interacting with the form.
From the tool's definition Tool description states 'Змінити назву, опис або налаштування форми' (Change form name, description, or settings), which are reversible modification operations on form metadata and configuration.
Attacks that exploit this kind of access
The rule that runs update_form 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, this is the rule to start with:
update_form 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 call is checked against it from then on.
Questions about update_form
Змінити назву, опис або налаштування форми. 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 accepts 5 parameters: desc, name, app_id, per_page, entity_id. 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: 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 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 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. 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 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