reorder_fields
Змінити порядок полів у формі. Передай масив field_id або field_name у бажаному порядку.
This record as markdown: /tools/com-quintadb-mcp/reorder-fields.md
What reorder_fields does on QuintaDB
AI agents use reorder_fields 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 |
|---|---|---|---|
order | array | Yes | Масив field_id або field_name у новому порядку (починаючи з позиції 0) |
app_id | string | Yes | Project ID (from list_projects) |
entity_id | string | Yes | Form ID (from list_forms or describe_project) |
Parameters from the server's own tool schema.
Why reorder_fields is rated Medium
Reordering form fields is a reversible modification to form configuration. It alters the presentation and structure of data collection but does not create, delete, or execute code. The change can be undone by reordering again. This fits the Write category (modifies data/configuration reversibly).
From the tool's definition Tool description (translated from Ukrainian) states: 'Change the order of fields in a form. Pass an array of field_id or field_name in the desired order.' This modifies the structure/layout of a form.
Attacks that exploit this kind of access
The rule that runs reorder_fields 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 reorder_fields, this is the rule to start with:
reorder_fields 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 reorder_fields call is checked against it from then on.
Questions about reorder_fields
Змінити порядок полів у формі. Передай масив field_id або field_name у бажаному порядку. 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.
reorder_fields accepts 3 parameters: order, app_id, entity_id. Required: order, 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 reorder_fields: 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.
reorder_fields 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 reorder_fields 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 reorder_fields. 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.
reorder_fields 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