Create a new Collective. Also creates the underlying Nextcloud Team. Optionally set an emoji icon.
AI agents use create_collective to create or update resources in Collectives — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Collectives environment.
This tool creates a new collective and associated Nextcloud Team, which are new data objects. Creation is reversible (the collective and team can be deleted), so this is a Write operation rather than Destructive. The severity is medium because creating many collectives could consume resources or clutter the workspace, but the action itself is not irreversible or dangerous.
From the tool's definition Tool name 'create_collective' and description 'Create a new Collective. Also creates the underlying Nextcloud Team.' indicate the tool creates new data structures reversibly.
Attacks that exploit this kind of access
Create a new Collective. Also creates the underlying Nextcloud Team. Optionally set an emoji icon. It is categorised as a Write tool in the Collectives MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Collectives MCP server in PolicyLayer and add a rule for create_collective: 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 Collectives. Nothing to install.
create_collective 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 create_collective 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 create_collective. 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.
create_collective is provided by the Collectives MCP server (megamaced/nc_collectives-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →