copy_entities · Elastic Brain ZH MCP: Risk & Policy

WHAT IT DOES

What copy_entities does on Elastic Brain ZH

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

WHY IT NEEDS A POLICY

Why copy_entities needs a policy

This tool creates new copies of entities (data duplication) rather than merely reading, which qualifies as Write. It does not permanently delete data (not Destructive), nor does it execute arbitrary code (not Execute).

From the tool's definition Tool name 'copy_entities' and description 'Copy entities between zones' indicates data duplication/replication across storage zones. The phrase 'with optional relation handling' suggests modification of entity relationships during the copy operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

copy_entities Rate-limited

copy_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": {
    "copy_entities": {
      "limits": [
        {
          "counter": "copy_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 Elastic Brain ZH, so you can run agents against it safely.

FAQ

Questions about copy_entities

What does the copy_entities tool do? +

Copy entities between zones with optional relation handling. It is categorised as a Write tool in the Elastic Brain ZH MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on copy_entities? +

Register the Elastic Brain ZH MCP server in PolicyLayer and add a rule for copy_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 Elastic Brain ZH. Nothing to install.

What risk level is copy_entities? +

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

Can I rate-limit copy_entities? +

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

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

copy_entities is provided by the Elastic Brain ZH MCP server (tocharianou/elastic-brain-zh). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.