AI agents use promote_chapter_item 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.
The tool modifies the state and location of chapter-level items (moving them between states: active queue → chapter notes or archive), which is a reversible write operation. While it changes data organization, it does not permanently delete data (making it Write rather than Destructive) and does not execute arbitrary code or trigger external services.
From the tool's definition Tool description states it can 'move it into chapter notes or archive it as promoted', which constitutes modification of existing data structures within the book repository.
Attacks that exploit this kind of access
Promote a structured chapter-level idea or note out of the active queue. You can move it into chapter notes or archive it as promoted after using it in draft work. 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 promote_chapter_item: 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.
promote_chapter_item 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 promote_chapter_item 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 promote_chapter_item. 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.
promote_chapter_item 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.
promote_chapter_item is one line of Narrarium's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →