AI agents use promote_book_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 and reorganizes existing items within a book repository system by changing their status and location (move to notes, move to story design, or archive). These are Write operations because they create or modify data reversibly—items can be moved again or recovered from archive.
From the tool's definition Tool performs state-change operations on book repository items: 'move it into notes or story design, or archive it as promoted'. These are reversible modifications to metadata and organizational structure.
Attacks that exploit this kind of access
Promote a structured book-level idea or note out of the active queue. You can move it into notes or story design, or archive it as promoted after you already used it in a draft. 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_book_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_book_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_book_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_book_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_book_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.
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 →