restore_trashed_collective · Collectives MCP: Risk & Policy

WHAT IT DOES

What restore_trashed_collective does on Collectives

AI agents use restore_trashed_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 restore_trashed_collective needs a policy

Restoration of soft-deleted data is a reversible write operation—it modifies state by un-deleting a resource, but the original deletion was soft (not permanent destruction). The blast radius is medium: restoring a collective could expose previously-hidden data to users and affect collaborative workflows, but the action itself is recoverable (the collective can be re-deleted).

From the tool's definition Tool name: 'restore_trashed_collective'; description: 'Restore a soft-deleted Collective from the trash.' This reverses a soft-delete operation (previously deleted data is recovered).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_trashed_collective Rate-limited

restore_trashed_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": {
    "restore_trashed_collective": {
      "limits": [
        {
          "counter": "restore_trashed_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 restore_trashed_collective

What does the restore_trashed_collective tool do? +

Restore a soft-deleted Collective from the trash. 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 restore_trashed_collective? +

Register the Collectives MCP server in PolicyLayer and add a rule for restore_trashed_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 restore_trashed_collective? +

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

Can I rate-limit restore_trashed_collective? +

Yes. Add a rate_limit block to the restore_trashed_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 restore_trashed_collective completely? +

Set action: deny in the PolicyLayer policy for restore_trashed_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 restore_trashed_collective? +

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