update_collective · Collectives MCP: Risk & Policy

WHAT IT DOES

What update_collective does on Collectives

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_collective needs a policy

The tool modifies collective configuration or metadata reversibly. It is not destructive (no deletion), not financial, not executable code. It is Write-category because it creates or modifies data reversibly. Severity is medium because unexpected collective modifications could affect collaboration workflows and visibility to team members, but changes are typically reversible via subsequent updates.

From the tool's definition Tool name 'update_collective' and description 'Change a Collective' indicate modification of existing collective data. Sibling tools include destructive operations (delete_collective, delete_page) but this tool itself only changes/modifies, not deletes.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_collective Rate-limited

update_collective 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": {
    "update_collective": {
      "limits": [
        {
          "counter": "update_collective_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Collectives, so you can run agents against it safely.

FAQ

Questions about update_collective

What does the update_collective tool do? +

Change a Collective\. 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.

How do I enforce a policy on update_collective? +

Register the Collectives MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_collective? +

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

Can I rate-limit update_collective? +

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

How do I block update_collective completely? +

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

What MCP server provides update_collective? +

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