Create a reader persona file in personas/ of the book repository. Personas represent fictional reader archetypes used to review chapters from different perspectives. Each persona has reading habits, values, dislikes, beauty and readability focus areas, emotional triggers, and tolerance scores. Us...
AI agents use create_persona 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 creates a new data file (persona) in the repository, which is a reversible write operation. The data being created is non-sensitive metadata about fictional reader archetypes for narrative review purposes. It has no destructive, financial, or execute-like effects, and does not retrieve existing data. The blast radius of misuse is minimal—creating unwanted personas can be easily deleted or overwritten.
From the tool's definition Create a reader persona file in personas/ of the book repository.
Attacks that exploit this kind of access
Create a reader persona file in personas/ of the book repository. Personas represent fictional reader archetypes used to review chapters from different perspectives. Each persona has reading habits, values, dislikes, beauty and readability focus areas, emotional triggers, and tolerance scores. Use seed_default_personas to populate the book with the five built-in archetypes instead of creating one manually. 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 create_persona: 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.
create_persona 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 create_persona 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 create_persona. 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.
create_persona 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 →