circles_create
Create a new circle/team. The current user becomes the owner. Set personal=true for a private circle only visible to the owner.
This record as markdown: /tools/aiquila-nextcloud-mcp-server/circles-create.md
What circles_create does on AIquila — Nextcloud MCP Server
AI agents use circles_create 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 |
|---|---|---|---|
name | string | Yes | Name for the new circle |
local | boolean | — | Restrict to local instance, no federation (default: false) |
personal | boolean | — | Create as a personal circle (default: false) |
Parameters from the server's own tool schema.
Why circles_create is rated Medium
This tool creates new data structures (circles/teams) within Nextcloud, which is a reversible write operation. While it affects group membership and visibility settings, it does not delete data, execute arbitrary code, move financial resources, or perform irreversible destructive operations.
From the tool's definition Tool description explicitly states 'Create a new circle/team', which is a creation action. The tool modifies system state by introducing new organizational entities and assigning ownership.
Attacks that exploit this kind of access
The rule that runs circles_create 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 circles_create, this is the rule to start with:
circles_create 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 circles_create call is checked against it from then on.
Questions about circles_create
Create a new circle/team. The current user becomes the owner. Set personal=true for a private circle only visible to the owner. 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.
circles_create accepts 3 parameters: name, local, personal. Required: name. 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 circles_create: 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.
circles_create 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 circles_create 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 circles_create. 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.
circles_create 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