AI agents use create_item 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 new data structures (item files) in a reversible manner typical of Write operations. While it adds content to the Narrarium repository, it does not execute arbitrary code, delete data, or cause financial impact. The reversibility of creation (items can be edited or removed) and the write-focused nature place this in the Write category.
From the tool's definition Tool description states it will 'Create a rich item file' with various attributes. The verb 'Create' and the action of generating a new file with structured data (appearance, purpose, significance, ownership) clearly indicates data creation.
Attacks that exploit this kind of access
Create a rich item file with appearance, purpose, significance, ownership, and optional historical research support. 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_item: 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_item 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_item 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_item. 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_item 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 →