move_entities

THE RISK

Critical Risk

Why move_entities needs a policy

The tool performs a copy followed by a delete from the source zone. The deletion from the source is irreversible, making this a Destructive operation. Misuse by an AI agent could result in entities being permanently removed from their source zone (even if copied to a destination), and if the copy step fails or the destination is wrong, data loss could occur.

From the tool's definition Move entities between zones (copy + delete from source)

Documented attack patterns abuse exactly the kind of access move_entities gives an agent:

POLICY

How to control move_entities

PolicyLayer is an MCP gateway — it sits between your AI agents and Elasticsearch Knowledge Graph for MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for move_entities:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "move_entities"
  ]
}

move_entities disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Elasticsearch Knowledge Graph for MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Elasticsearch Knowledge Graph for MCP tools

Destructive delete_entities Delete multiple entities and their associated relations from the knowledge graph Destructive delete_observations Delete specific observations from entities in the knowledge graph Destructive delete_relations Delete multiple relations from the knowledge graph Destructive delete_zone Delete a memory zone and all its entities/relations. Write add_observations Add new observations to existing entities in the knowledge graph Write copy_entities Copy entities between zones with optional relation handling. Write create_entities Create multiple new entities in the knowledge graph Write create_relations Create multiple new relations between entities in the knowledge graph. Relations should be

All 23 Elasticsearch Knowledge Graph for MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Elasticsearch Knowledge Graph for MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about move_entities

What does the move_entities tool do? +

Move entities between zones (copy + delete from source). It is categorised as a Destructive tool in the Elasticsearch Knowledge Graph for MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on move_entities? +

Register the Elasticsearch Knowledge Graph for MCP server in PolicyLayer and add a rule for move_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 Elasticsearch Knowledge Graph for MCP. Nothing to install.

What risk level is move_entities? +

move_entities is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit move_entities? +

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

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

move_entities is provided by the Elasticsearch Knowledge Graph for MCP server (j3k0/mcp-brain-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Elasticsearch Knowledge Graph for MCP tool call.

Start from Elasticsearch Knowledge Graph for MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →