register_new_relation · Alethea World History Engine MCP

WHAT IT DOES

What register_new_relation does on Alethea World History Engine

AI agents use register_new_relation 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.

WHY IT NEEDS A POLICY

Why register_new_relation needs a policy

This tool creates or modifies data (relation types) in the world-building graph engine. It is reversible since updates occur in runtime memory and are not automatically persisted to permanent storage. This fits the Write category (creates/modifies data reversibly).

From the tool's definition Tool description states 'Register a new relation TYPE', which creates a new relation type in the narrative graph engine's runtime.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

register_new_relation Rate-limited

register_new_relation stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "register_new_relation": {
      "limits": [
        {
          "counter": "register_new_relation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Alethea World History Engine, so you can run agents against it safely.

FAQ

Questions about register_new_relation

What does the register_new_relation tool do? +

Register a new relation TYPE. (Note: Only updates Runtime, usually doesn't need save unless types are persisted separately). 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.

How do I enforce a policy on register_new_relation? +

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

register_new_relation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit register_new_relation? +

Yes. Add a rate_limit block to the register_new_relation 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 register_new_relation completely? +

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

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