update_form_option
Update a choice option's text (and optionally its order).
This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-form-option.md
What update_form_option does on AIquila — Nextcloud MCP Server
AI agents use update_form_option to create or update resources in AIquila — Nextcloud MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AIquila — Nextcloud MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
text | string | — | |
order | integer | — | |
formId | integer | Yes | Form ID |
optionId | integer | Yes | Option ID |
questionId | integer | Yes | Question ID |
Parameters from the server's own tool schema.
Why update_form_option is rated Medium
This tool creates or modifies data in a reversible manner without deleting or executing code. Users can update form options and later revert changes. Impact is medium severity because misconfiguration of form options could disrupt workflows for users relying on forms, but the effect is limited to metadata/UI elements rather than critical data destruction or financial operations.
From the tool's definition Tool explicitly performs 'Update' operation on form choice options, modifying option text and order. Description confirms reversible modification capability.
Attacks that exploit this kind of access
The rule that runs update_form_option safely
PolicyLayer is an MCP gateway: it sits between your AI agents and AIquila — Nextcloud MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_form_option, this is the rule to start with:
update_form_option 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 AIquila — Nextcloud MCP Server, apply this rule, and every update_form_option call is checked against it from then on.
Questions about update_form_option
Update a choice option's text (and optionally its order). It is categorised as a Write tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
update_form_option accepts 5 parameters: text, order, formId, optionId, questionId. Required: formId, optionId, questionId. The full parameter table on this page comes from the server's own tool schema.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for update_form_option: 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 AIquila — Nextcloud MCP Server. Nothing to install.
update_form_option 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_option 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_option. 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_option is provided by the AIquila — Nextcloud MCP Server MCP server (elgorro/aiquila). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on AIquila — Nextcloud MCP Server, and thousands of servers like it.
This server
Across the catalogue