AI agents use rename_paragraph 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.
This tool creates or modifies metadata and file structures within the book repository. While it involves file movement and renaming, these are reversible operations that do not delete data or cause irreversible damage. The blast radius is moderate—incorrect renaming could corrupt cross-references or asset organization within the repository, but changes can be undone.
From the tool's definition The tool 'rename_paragraph' performs operations that modify and reorganize data: 'Rename a paragraph or scene title or number, move its markdown file, and move any matching paragraph asset folder if present.' These are reversible write operations (renaming…
Attacks that exploit this kind of access
Rename a paragraph or scene title or number, move its markdown file, and move any matching paragraph asset folder 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.
Register the Narrarium MCP server in PolicyLayer and add a rule for rename_paragraph: 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.
rename_paragraph is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the rename_paragraph 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.
Set action: deny in the PolicyLayer policy for rename_paragraph. 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.
rename_paragraph 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →