Available Tags, EntityTypes, and RelationTypes.
AI agents call get_world_metadata 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 metadata about the world configuration. It queries and returns information without creating, modifying, deleting, or executing anything. It has no side effects and no capability to alter the fictional world state. Similar to other Read-category tools in the sibling set (get_entity_details, get_registry_status, get_relationship_table, list_template_schemas, query_entities).
From the tool's definition Tool name is 'get_world_metadata' and description states it retrieves 'Available Tags, EntityTypes, and RelationTypes' — pure data retrieval with no mutation or side effects.
Attacks that exploit this kind of access
Available Tags, EntityTypes, and RelationTypes. 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 get_world_metadata: 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.
get_world_metadata 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 get_world_metadata 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 get_world_metadata. 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.
get_world_metadata 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 →