get_relationship_table

get_relationship_table

Server Alethea World History Engine watashicuvu/world-history-engine
Category Read
Risk class Low
Parameters 00 required

What get_relationship_table does on Alethea World History Engine

AI agents call get_relationship_table 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.

Why get_relationship_table needs a policy

The tool name and context suggest this retrieves or queries relationship data from the narrative graph engine, consistent with Read operations that access but do not modify state. Confidence is moderate (0.75) due to the empty description, but the naming convention and server design context strongly suggest a read-only operation for inspecting relationships between entities in the fictional world model.

From the tool's definition Tool name 'get_relationship_table' indicates retrieval of relational data without modification. The empty description and sibling tools like 'query_entities', 'get_entity_details', and 'get_world_metadata' (all Read operations) establish the pattern for this…

Questions about get_relationship_table

What does the get_relationship_table tool do? +

get_relationship_table. It is categorised as a Read tool in the Alethea World History Engine MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_relationship_table? +

Register the Alethea World History Engine MCP server in PolicyLayer and add a rule for get_relationship_table: 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.

What risk level is get_relationship_table? +

get_relationship_table is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_relationship_table? +

Yes. Add a rate_limit block to the get_relationship_table 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.

How do I block get_relationship_table completely? +

Set action: deny in the PolicyLayer policy for get_relationship_table. 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.

What MCP server provides get_relationship_table? +

get_relationship_table 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.