AI agents use update_chapter_draft 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 modifies existing chapter draft data (frontmatter and body content) but does not delete or destroy data irreversibly. The changes are reversible through subsequent updates. It is a Write operation rather than Destructive since it creates or modifies data reversibly.
From the tool's definition Tool description explicitly states 'Update an existing chapter draft by patching its frontmatter and replacing or appending rough draft body content.' The verbs 'patching', 'replacing', and 'appending' indicate reversible modification of data.
Attacks that exploit this kind of access
Update an existing chapter draft by patching its frontmatter and replacing or appending rough draft body content. 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 update_chapter_draft: 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.
update_chapter_draft 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 update_chapter_draft 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 update_chapter_draft. 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.
update_chapter_draft 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 →