list_form_submissions
List submissions for a form. Supports free-text search (query) and pagination (limit/offset). Only form owners/admins see all submissions.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/list-form-submissions.md
What list_form_submissions does on AIquila — Nextcloud MCP Server
AI agents call list_form_submissions to retrieve information from AIquila — Nextcloud MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | Max submissions to return |
query | string | — | Free-text search across answer values |
formId | integer | Yes | Form ID |
offset | integer | — | Offset for pagination |
Parameters from the server's own tool schema.
Why list_form_submissions is rated Low
This tool retrieves and queries existing form submission data with search and pagination support. It has no side effects, does not modify or delete data, and does not execute external operations. The access control mechanism further limits blast radius. This is a straightforward Read operation.
From the tool's definition Tool name 'list_form_submissions' and description 'List submissions for a form' indicate data retrieval only. No modifications, deletions, executions, or financial operations are performed.
Attacks that exploit this kind of access
The rule that runs list_form_submissions 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 list_form_submissions, this is the rule to start with:
list_form_submissions is read-only, so it stays allowed. 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 list_form_submissions call is checked against it from then on.
Questions about list_form_submissions
List submissions for a form. Supports free-text search (query) and pagination (limit/offset). Only form owners/admins see all submissions. It is categorised as a Read tool in the AIquila — Nextcloud MCP Server MCP Server, which means it retrieves data without modifying state.
list_form_submissions accepts 4 parameters: limit, query, formId, offset. Required: formId. 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 list_form_submissions: 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.
list_form_submissions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_form_submissions 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 list_form_submissions. 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.
list_form_submissions 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