create_form_submission
Submit answers to a form. answers is an object keyed by question ID; values are always arrays. For text questions: ["My answer"]. For choice questions: [optionId1, optionId2] (numeric IDs). Public links require shareHash.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/create-form-submission.md
What create_form_submission does on AIquila — Nextcloud MCP Server
AI agents use create_form_submission 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 |
|---|---|---|---|
formId | integer | Yes | Form ID |
answers | object | Yes | Object keyed by question ID; each value is an array of strings or option IDs |
shareHash | string | — | Share hash — required when submitting via a public link |
Parameters from the server's own tool schema.
Why create_form_submission is rated Medium
This tool creates new form submission data in a Nextcloud instance. While submissions are typically reversible and don't inherently destroy data, the act of submitting form answers represents a Write operation that creates persistent records.
From the tool's definition Tool description states it 'Submit answers to a form' and accepts answers that are stored (keyed by question ID), indicating data creation/modification. The tool creates form submission records in Nextcloud.
Attacks that exploit this kind of access
The rule that runs create_form_submission 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 create_form_submission, this is the rule to start with:
create_form_submission 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 create_form_submission call is checked against it from then on.
Questions about create_form_submission
Submit answers to a form. answers is an object keyed by question ID; values are always arrays. For text questions: ["My answer"]. For choice questions: [optionId1, optionId2] (numeric IDs). Public links require shareHash. 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.
create_form_submission accepts 3 parameters: formId, answers, shareHash. Required: formId, answers. 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 create_form_submission: 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.
create_form_submission 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 create_form_submission 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 create_form_submission. 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.
create_form_submission 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