update_entity_tags · Alethea World History Engine MCP

WHAT IT DOES

What update_entity_tags does on Alethea World History Engine

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

This tool creates or modifies data (tags and state) within the narrative graph engine in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The 'save state' operation suggests persistence of changes, but tag updates are typically reversible edits.

From the tool's definition Tool name is 'update_entity_tags' and description states it 'Update tags AND save state.' The verb 'update' and explicit mention of 'save state' indicate modification of existing data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_entity_tags Rate-limited

update_entity_tags 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": {
    "update_entity_tags": {
      "limits": [
        {
          "counter": "update_entity_tags_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 update_entity_tags

What does the update_entity_tags tool do? +

Update tags AND save state. 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 update_entity_tags? +

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

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

Can I rate-limit update_entity_tags? +

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

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

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