Create multiple new entities in the knowledge graph
AI agents use create_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.
The tool creates new entities in the knowledge graph, which is a reversible write operation. It modifies the stored data structure but does not execute arbitrary code, delete data irreversibly, or move financial resources.
From the tool's definition Tool name 'create_entities' and description 'Create multiple new entities in the knowledge graph' indicate data creation/addition operations.
Attacks that exploit this kind of access
Create multiple new entities in the knowledge graph. 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.
Register the Elastic Brain ZH MCP server in PolicyLayer and add a rule for create_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.
create_entities is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →