rename_chapter · Narrarium MCP: Risk & Policy

WHAT IT DOES

What rename_chapter does on Narrarium

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

WHY IT NEEDS A POLICY

Why rename_chapter needs a policy

This tool performs reversible modifications to chapter metadata and folder structures within a book repository. It does not delete data (making it less severe than Destructive), does not execute arbitrary code or external operations (not Execute), and does not involve financial transactions (not Financial).

From the tool's definition The tool 'rename_chapter' creates or modifies data by renaming chapter titles/numbers and moving folders. The description explicitly states it performs rename and move operations on chapters and asset folders.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

rename_chapter Rate-limited

rename_chapter 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_chapter": {
      "limits": [
        {
          "counter": "rename_chapter_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 Narrarium, so you can run agents against it safely.

FAQ

Questions about rename_chapter

What does the rename_chapter tool do? +

Rename a chapter title or number, move its folder, and move any matching chapter or paragraph asset folders if present. It is categorised as a Write tool in the Narrarium 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_chapter? +

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

What risk level is rename_chapter? +

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

Can I rate-limit rename_chapter? +

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

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

rename_chapter is provided by the Narrarium MCP server (narrarium-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.