AI agents call list_related_canon to retrieve information from Narrarium without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing canon file references based on a query or id. It has no side effects, does not modify data, and performs a straightforward search/lookup operation. The severity is low because the blast radius of misuse is minimal - it only exposes information already stored in the local repository with no destructive, financial, or irreversible consequences.
From the tool's definition Tool name 'list_related_canon' and description explicitly states it 'List[s] canon files' - a retrieval operation. The stated purpose is 'useful before writing scenes or revising continuity', indicating it queries existing data without modification.
Attacks that exploit this kind of access
List canon files that reference or mention a given id or query, useful before writing scenes or revising continuity. It is categorised as a Read tool in the Narrarium MCP Server, which means it retrieves data without modifying state.
Register the Narrarium MCP server in PolicyLayer and add a rule for list_related_canon: 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.
list_related_canon is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_related_canon 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 list_related_canon. 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.
list_related_canon 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 →