Create multiple new relations between entities in the knowledge graph. Relations should be in active voice
AI agents use create_relations 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 new relations in a knowledge graph, which is a write operation that modifies data. It is reversible (relations can be deleted) and has no financial impact or irreversible deletion.
From the tool's definition The tool description states it will 'Create multiple new relations between entities in the knowledge graph' - this is explicitly a create operation that modifies data in the knowledge graph.
Attacks that exploit this kind of access
Create multiple new relations between entities in the knowledge graph. Relations should be in active voice. 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_relations: 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_relations 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_relations 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_relations. 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_relations 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.
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 →