rename_page · Collectives MCP: Risk & Policy

WHAT IT DOES

What rename_page does on Collectives

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

Renaming a page modifies data but does not delete or irreversibly destroy content, does not execute arbitrary code or commands, and does not involve financial transactions. It is a standard write operation that changes a page attribute.

From the tool's definition Tool name 'rename_page' and description 'Rename a page within its current parent' indicate modification of an existing page's metadata (its name). This is a reversible write operation—the original name can be restored by renaming again.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_page Rate-limited

rename_page 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": {
    "rename_page": {
      "limits": [
        {
          "counter": "rename_page_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 rename_page

What does the rename_page tool do? +

Rename a page within its current parent. 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 rename_page? +

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

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

Can I rate-limit rename_page? +

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

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

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