circles_add_member

Add a member to a circle/team. Requires moderator privileges or higher. Member type: 1=user (default), 2=group, 4=mail, 16=circle.

SERVERAIquila — Nextcloud MCP Server SOURCEelgorro/aiquila

Medium RISK CLASS

Category Write

Parameters 32 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/aiquila-nextcloud-mcp-server/circles-add-member.md

WHAT IT DOES

What circles_add_member does on AIquila — Nextcloud MCP Server

AI agents use circles_add_member 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
`type`	number	—	Member type: 1=user (default), 2=group, 4=mail, 8=contact, 16=circle
`userId`	string	Yes	The user ID (or entity identifier) to add
`circleId`	string	Yes	The circle ID to add the member to

Parameters from the server's own tool schema.

RISK

Why circles_add_member is rated Medium

This tool modifies Nextcloud group/circle membership by adding members, which is a write operation that creates new associations in the system. While it requires moderator privileges as a guard, an AI agent with those credentials could be tricked into adding unwanted members to circles, potentially granting access to sensitive shared resources.

From the tool's definition Tool name is 'circles_add_member' and description states 'Add a member to a circle/team', which creates a new membership relationship in the system. This is a reversible modification (members can be removed later).

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs circles_add_member 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_add_member, this is the rule to start with:

circles_add_member Rate-limited

circles_add_member 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "circles_add_member": {
      "limits": [
        {
          "counter": "circles_add_member_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect AIquila — Nextcloud MCP Server, apply this rule, and every circles_add_member call is checked against it from then on.

FAQ

Questions about circles_add_member

What does the circles_add_member tool do? +

Add a member to a circle/team. Requires moderator privileges or higher. Member type: 1=user (default), 2=group, 4=mail, 16=circle. 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.

What parameters does circles_add_member accept? +

circles_add_member accepts 3 parameters: type, userId, circleId. Required: userId, circleId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on circles_add_member? +

Register the AIquila — Nextcloud MCP Server MCP server in PolicyLayer and add a rule for circles_add_member: 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.

What risk level is circles_add_member? +

circles_add_member is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit circles_add_member? +

Yes. Add a rate_limit block to the circles_add_member 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.

How do I block circles_add_member completely? +

Set action: deny in the PolicyLayer policy for circles_add_member. 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.

What MCP server provides circles_add_member? +

circles_add_member 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.

KEEP EXPLORING

More on AIquila — Nextcloud MCP Server, and thousands of servers like it.

This server

All 301 AIquila — Nextcloud MCP Server tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →