define_new_archetype · Alethea World History Engine MCP

WHAT IT DOES

What define_new_archetype does on Alethea World History Engine

AI agents use define_new_archetype 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 define_new_archetype needs a policy

This tool creates a new archetype/template entry in the database. It is a write operation (creating new data) with no indication of irreversibility, financial impact, or code execution. Misuse would result in unwanted templates being added, which is a reversible side effect with low blast radius in a fictional world-building context.

From the tool's definition "Add a NEW template to the database"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

define_new_archetype Rate-limited

define_new_archetype 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": {
    "define_new_archetype": {
      "limits": [
        {
          "counter": "define_new_archetype_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 define_new_archetype

What does the define_new_archetype tool do? +

Add a NEW template to the database. 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 define_new_archetype? +

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

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

Can I rate-limit define_new_archetype? +

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

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

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