Creates a new world.
AI agents use generate_new_world to create or update resources in Alethea World History Engine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Alethea World History Engine environment.
This tool creates new data (a world) within the system, which is a reversible operation. It does not execute arbitrary code, delete data, or move financial resources. It falls under the Write category as it generates and initializes new entities in the narrative graph.
From the tool's definition Tool name 'generate_new_world' and description 'Creates a new world' explicitly indicate creation of data structures within the narrative graph engine.
Attacks that exploit this kind of access
Creates a new world. It is categorised as a Write tool in the Alethea World History Engine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Alethea World History Engine MCP server in PolicyLayer and add a rule for generate_new_world: 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.
generate_new_world 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 generate_new_world 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 generate_new_world. 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.
generate_new_world 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 →