update_terms_settings
Update the Terms of Service enforcement settings: whether logged-in users must accept the terms (tos_for_users) and whether the terms apply to public shares (tos_on_public_shares). Requires the configured Nextcloud user to be an admin.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/update-terms-settings.md
What update_terms_settings does on AIquila — Nextcloud MCP Server
AI agents use update_terms_settings 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 |
|---|---|---|---|
tosForUsers | boolean | — | Require logged-in users to accept the terms |
tosOnPublicShares | boolean | — | Apply the terms to public shares |
Parameters from the server's own tool schema.
Why update_terms_settings is rated Medium
This tool creates or modifies configuration data (ToS enforcement policies) that can affect all users of the Nextcloud instance. While not destructive (changes are reversible), it is clearly a Write operation that changes system settings.
From the tool's definition Tool description states it "Update[s] the Terms of Service enforcement settings" including whether terms apply to logged-in users and public shares. This modifies configuration settings that affect the entire Nextcloud instance.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs update_terms_settings 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_terms_settings, this is the rule to start with:
update_terms_settings 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 update_terms_settings call is checked against it from then on.
Questions about update_terms_settings
Update the Terms of Service enforcement settings: whether logged-in users must accept the terms (tos_for_users) and whether the terms apply to public shares (tos_on_public_shares). Requires the configured Nextcloud user to be an admin. 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.
update_terms_settings accepts 2 parameters: tosForUsers, tosOnPublicShares. 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 update_terms_settings: 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.
update_terms_settings 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 update_terms_settings 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 update_terms_settings. 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.
update_terms_settings 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