Create multiple new entities in the knowledge graph
AI agents use create_entities to create or update resources in Helm Chart CLI — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Helm Chart CLI environment.
This tool creates entities in a knowledge graph, which is a reversible write operation. The high severity reflects the potential impact of creating multiple entities that could corrupt or pollute the knowledge graph, especially if an AI agent makes mistakes about what entities should exist.
From the tool's definition Tool is named 'create_entities' and described as 'Create multiple new entities in the knowledge graph' — explicitly creates new data.
Attacks that exploit this kind of access
Create multiple new entities in the knowledge graph. It is categorised as a Write tool in the Helm Chart CLI MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Helm Chart CLI 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 Helm Chart CLI. 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 Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
create_entities is one line of Helm Chart CLI's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →