get_registry_status
AI agents call get_registry_status 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.
The tool retrieves status information about the registry without modifying state. Although the description is empty, the naming pattern and context among sibling tools strongly suggest a non-destructive query operation. No side effects, data modification, or external execution are implied. Severity is low because status reads have minimal blast radius even if misused.
From the tool's definition Tool name 'get_registry_status' indicates a query/retrieval operation consistent with other Read-category sibling tools on this server (get_entity_details, get_relationship_table, get_template_list, get_world_metadata, list_template_schemas, query_entities).
Attacks that exploit this kind of access
get_registry_status. 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_registry_status: 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_registry_status 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_registry_status 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_registry_status. 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_registry_status 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 →