transfer_form_owner
Transfer ownership of a form to another Nextcloud user. The new owner must have access to the Forms app.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/transfer-form-owner.md
What transfer_form_owner does on AIquila — Nextcloud MCP Server
AI agents use transfer_form_owner 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.
Why transfer_form_owner is rated Medium
Transferring ownership of a form modifies access control and ownership metadata in a reversible way (ownership could potentially be transferred back), making it a Write operation. However, the blast radius is high because an AI agent could reassign ownership of sensitive forms to unintended users, potentially causing data loss of control or unauthorized access to form data and responses.
From the tool's definition Transfer ownership of a form to another Nextcloud user
Attacks that exploit this kind of access
The rule that runs transfer_form_owner 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 transfer_form_owner, this is the rule to start with:
transfer_form_owner 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 transfer_form_owner call is checked against it from then on.
Questions about transfer_form_owner
Transfer ownership of a form to another Nextcloud user. The new owner must have access to the Forms app. 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.
Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for transfer_form_owner: 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.
transfer_form_owner 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 transfer_form_owner 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 transfer_form_owner. 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.
transfer_form_owner 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