Medium Risk

renumber_pages

주어진 변경 목록(changes)에 따라 페이지 번호를 일괄 변경합니다. dry_run=True(기본값)로 실행하여 diff를 확인한 후, dry_run=False로 실제 변경을 수행하세요.

How to control renumber_pages ↓

What renumber_pages does on Wikidocs

AI agents use renumber_pages to create or update resources in Wikidocs — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wikidocs environment.

Medium Risk

Why renumber_pages needs a policy

This tool performs bulk renumbering of pages, which is a reversible write operation modifying page metadata across potentially many pages. The bulk nature (일괄 변경) increases blast radius — a misuse could scramble the entire book's page ordering — justifying high severity. It is not destructive in the sense of permanent deletion, but the wide-scale modification warrants high severity.

From the tool's definition '페이지 번호를 일괄 변경합니다' (bulk changes page numbers according to a given change list) and 'dry_run=False로 실제 변경을 수행하세요' (perform actual changes with dry_run=False)

Documented attack patterns abuse exactly the kind of access renumber_pages gives an agent:

How to control renumber_pages

PolicyLayer is an MCP gateway — it sits between your AI agents and Wikidocs, and nothing reaches the server without passing your rules. This is the rule we recommend for renumber_pages:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "renumber_pages": {
      "limits": [
        {
          "counter": "renumber_pages_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Wikidocs — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about renumber_pages

What does the renumber_pages tool do? +

주어진 변경 목록(changes)에 따라 페이지 번호를 일괄 변경합니다. dry_run=True(기본값)로 실행하여 diff를 확인한 후, dry_run=False로 실제 변경을 수행하세요. It is categorised as a Write tool in the Wikidocs MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on renumber_pages? +

Register the Wikidocs MCP server in PolicyLayer and add a rule for renumber_pages: 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 Wikidocs. Nothing to install.

What risk level is renumber_pages? +

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

Can I rate-limit renumber_pages? +

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

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

renumber_pages is provided by the Wikidocs MCP server (ychoi-kr/wikidocs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Wikidocs tool call.

Start from Wikidocs, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

17 Wikidocs tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.