Get JSON Schema for a template.
AI agents call list_template_schemas to retrieve information from Alethea World History Engine without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves schema definitions for templates within the narrative graph engine. It performs a read-only query operation with no side effects—it does not create, modify, delete, execute code, or affect any state. The blast radius of misuse is minimal, as an AI agent gaining access to schema information cannot cause damage to the world state or financial systems.
From the tool's definition Tool name 'list_template_schemas' and description 'Get JSON Schema for a template' indicate a retrieval operation that queries and returns template schema information without modifying data.
Attacks that exploit this kind of access
Get JSON Schema for a template. It is categorised as a Read tool in the Alethea World History Engine MCP Server, which means it retrieves data without modifying state.
Register the Alethea World History Engine MCP server in PolicyLayer and add a rule for list_template_schemas: 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 Alethea World History Engine. Nothing to install.
list_template_schemas 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_template_schemas 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_template_schemas. 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_template_schemas is provided by the Alethea World History Engine MCP server (watashicuvu/world-history-engine). 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 →