Assemble the point-in-time context that should be read before writing or polishing a chapter: prose defaults, scoped story-so-far context, prior chapter state, and matching chapter draft without leaking later story material. In prose, keep canon names as plain text instead of markdown links; the ...
AI agents call chapter_writing_context to retrieve information from Narrarium without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool gathers and presents existing data from a book repository to support writing decisions. It reads/queries story context, draft information, and defaults without creating, modifying, deleting, or executing operations. The instruction to 'keep canon names as plain text' is a display preference, not a data mutation.
From the tool's definition Tool description states it 'Assemble[s]' and retrieves 'context that should be read before writing' including 'prose defaults, scoped story-so-far context, prior chapter state, and matching chapter draft' — this is a retrieval/query operation with no side…
Attacks that exploit this kind of access
Assemble the point-in-time context that should be read before writing or polishing a chapter: prose defaults, scoped story-so-far context, prior chapter state, and matching chapter draft without leaking later story material. In prose, keep canon names as plain text instead of markdown links; the reader resolves visible mentions. It is categorised as a Read tool in the Narrarium MCP Server, which means it retrieves data without modifying state.
Register the Narrarium MCP server in PolicyLayer and add a rule for chapter_writing_context: 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.
chapter_writing_context is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the chapter_writing_context 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 chapter_writing_context. 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.
chapter_writing_context 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 →