AI agents use update_script 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 content in a structured, versioned repository (book/writing project). Changes are reversible—prior versions can be restored and edits can be undone. It does not delete content (would be Destructive) or execute arbitrary code (would be Execute). The scope is limited to updating scene scripts and metadata within a local Narrarium repository.
From the tool's definition Tool description states "Update an existing scene script" and "refine beats, add new lines, or patch frontmatter". These are reversible modifications to existing data (scripts/<chapter>/<paragraph>.md).
Attacks that exploit this kind of access
Update an existing scene script in scripts/<chapter>/<paragraph>.md. Use this to refine beats, add new lines, or patch frontmatter (e.g. change location or tags). Provide \. 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_script: 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_script 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_script 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_script. 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_script 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 →