Answer a natural-language canon question by combining structured state, summaries, chapters, and repository search. Use this for questions like where a character is, what they know, who holds a secret, when something first appears, or how a relationship/condition/open loop changes across a chapte...
AI agents call query_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 queries existing data from a book repository (character locations, knowledge, plot timelines, relationships) without creating, modifying, deleting, or executing external operations. It performs informational lookups only, making it a Read category tool with low severity since misuse would merely return incorrect or irrelevant information about fictional canon.
From the tool's definition Tool description states it 'Answer[s] a natural-language canon question' and is used to query information about characters, events, and relationships.
Attacks that exploit this kind of access
Answer a natural-language canon question by combining structured state, summaries, chapters, and repository search. Use this for questions like where a character is, what they know, who holds a secret, when something first appears, or how a relationship/condition/open loop changes across a chapter range. 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 query_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.
query_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 query_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 query_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.
query_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 →