AI agents use wizard_finalize 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 writes files or folders to a local repository, creating or modifying content. This is a Write operation as it creates/saves data to the filesystem. While it could overwrite existing files, the description doesn't explicitly indicate irreversible deletion, so Destructive is not clearly applicable.
From the tool's definition Finalize a wizard session and write the corresponding file or folder into the local book repository
Attacks that exploit this kind of access
Finalize a wizard session and write the corresponding file or folder into the local book repository. 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 wizard_finalize: 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.
wizard_finalize 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 wizard_finalize 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 wizard_finalize. 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.
wizard_finalize 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 →