restore_page_version · Collectives MCP: Risk & Policy

WHAT IT DOES

What restore_page_version does on Collectives

AI agents use restore_page_version 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_page_version needs a policy

This tool modifies page content by replacing it with historical content, which qualifies as a Write operation. Although it affects data state, the operation is reversible (the current version is automatically preserved as a version entry, and another restore can undo this action). It is not Destructive because no data is irreversibly deleted; not Execute because it does not run arbitrary code; not Financial.

From the tool's definition Tool description states 'The current content is replaced with the selected version (the current version is preserved as a new version entry)' — a modification operation that is reversible by restoring a different version.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

restore_page_version Rate-limited

restore_page_version 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_page_version": {
      "limits": [
        {
          "counter": "restore_page_version_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_page_version

What does the restore_page_version tool do? +

Restore a specific historical version of a page. The current content is replaced with the selected version (the current version is preserved as a new version entry). 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_page_version? +

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

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

Can I rate-limit restore_page_version? +

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

Set action: deny in the PolicyLayer policy for restore_page_version. 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_page_version? +

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