update_form

Update form properties. Only provided fields are changed. state: 0=active, 1=closed, 2=archived. expires=0 disables expiration.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 101 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-form.md

WHAT IT DOES

What update_form does on AIquila — Nextcloud MCP Server

AI agents use update_form 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
`state`	object	—
`title`	string	—
`formId`	integer	Yes	Form ID
`expires`	integer	—	Unix timestamp; 0 = no expiration
`description`	string	—
`isAnonymous`	boolean	—
`showExpiration`	boolean	—
`submitMultiple`	boolean	—
`submissionMessage`	string	—
`allowEditSubmissions`	boolean	—

Parameters from the server's own tool schema.

RISK

Why update_form is rated Medium

This tool modifies form configuration data (state transitions, expiration settings) reversibly. Changes can be undone by updating again, so it falls under Write rather than Destructive. The medium severity reflects that unauthorized form modifications could disrupt workflows or affect data collection, but the changes are not irreversible and don't involve financial transactions or code execution.

From the tool's definition Tool name 'update_form' and description 'Update form properties. Only provided fields are changed' indicates modification of existing data (form state, expiration settings).

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_form Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_form": {
      "limits": [
        {
          "counter": "update_form_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 AIquila — Nextcloud MCP Server, apply this rule, and every update_form call is checked against it from then on.

FAQ

Questions about update_form

What does the update_form tool do? +

Update form properties. Only provided fields are changed. state: 0=active, 1=closed, 2=archived. expires=0 disables expiration. 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.

What parameters does update_form accept? +

update_form accepts 10 parameters: state, title, formId, expires, description, isAnonymous, showExpiration, submitMultiple, submissionMessage, allowEditSubmissions. Required: formId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_form? +

Register the AIquila — Nextcloud MCP Server 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 AIquila — Nextcloud MCP Server. Nothing to install.

What risk level is update_form? +

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

Can I rate-limit update_form? +

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.

How do I block update_form completely? +

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.

What MCP server provides update_form? +

update_form 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.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

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