delete_form_submission
Delete a single submission by ID.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/delete-form-submission.md
What delete_form_submission does on AIquila — Nextcloud MCP Server
AI agents call delete_form_submission to permanently remove resources in AIquila — Nextcloud MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
formId | integer | Yes | Form ID |
submissionId | integer | Yes | Submission ID |
Parameters from the server's own tool schema.
Why delete_form_submission is rated Critical
This tool permanently removes form submission data, which cannot be undone. Destructive is more severe than Write (reversible modifications) and applies when data deletion is the core function. The high severity reflects that loss of submission records could impact data integrity, compliance, and user records in a Nextcloud environment.
From the tool's definition Tool name 'delete_form_submission' and description 'Delete a single submission by ID' explicitly indicate irreversible deletion of data.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_form_submission, this is the rule to start with:
delete_form_submission is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every delete_form_submission call is checked against it from then on.
Questions about delete_form_submission
Delete a single submission by ID. It is categorised as a Destructive tool in the AIquila — Nextcloud MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_form_submission accepts 2 parameters: formId, submissionId. Required: formId, submissionId. 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 delete_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.
delete_form_submission is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_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 delete_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.
delete_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.
Across the catalogue