Find entities in the graph.
AI agents call query_entities 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 or searches for entities within the fictional world graph without creating, modifying, deleting, or executing external operations. It fits the Read category as a query operation that returns existing data. Severity is low because misuse would only expose narrative data without causing system damage or irreversible changes.
From the tool's definition Tool name 'query_entities' combined with description 'Find entities in the graph' indicates a search/retrieval operation.
Attacks that exploit this kind of access
Find entities in the graph. 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 query_entities: 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.
query_entities 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_entities 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_entities. 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_entities 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 →