batch_add_entities · Loenn MCP: Risk & Policy

WHAT IT DOES

What batch_add_entities does on Loenn

AI agents use batch_add_entities to create or update resources in Loenn — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Loenn environment.

WHY IT NEEDS A POLICY

Why batch_add_entities needs a policy

This tool creates or modifies map entities in bulk within Celeste .bin files. While reversible (entities can be removed), bulk addition poses a high-severity risk if an AI agent misconfigures entity properties, adds incompatible entities, or corrupts the map structure. The lack of description lowers confidence slightly, but sibling context and naming convention are clear indicators of Write category.

From the tool's definition Tool name is 'batch_add_entities' with verb 'batch_add', indicating creation of multiple entities. Sibling tools like 'add_entity', 'add_room', 'add_trigger' are confirmed Write operations on .bin map files.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch_add_entities Rate-limited

batch_add_entities 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": {
    "batch_add_entities": {
      "limits": [
        {
          "counter": "batch_add_entities_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 Loenn, so you can run agents against it safely.

FAQ

Questions about batch_add_entities

What does the batch_add_entities tool do? +

batch_add_entities. It is categorised as a Write tool in the Loenn MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on batch_add_entities? +

Register the Loenn MCP server in PolicyLayer and add a rule for batch_add_entities: 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 Loenn. Nothing to install.

What risk level is batch_add_entities? +

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

Can I rate-limit batch_add_entities? +

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

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

batch_add_entities is provided by the Loenn MCP server (magedeline/loenn-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.