Create multiple new entities in the project knowledge graph
AI agents use create_entities to create or update resources in Xgmem — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Xgmem environment.
This tool creates new knowledge graph entities, which modifies the knowledge graph in a reversible manner (entities can be deleted via delete_entities). It is Write rather than Execute because it performs a straightforward data creation operation without executing arbitrary code or shell commands.
From the tool's definition Tool name 'create_entities' and description 'Create multiple new entities in the project knowledge graph' indicate data creation.
Documented attack patterns abuse exactly the kind of access create_entities gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xgmem, and nothing reaches the server without passing your rules. This is the rule we recommend for create_entities:
{
"version": "1",
"default": "deny",
"tools": {
"create_entities": {
"limits": [
{
"counter": "create_entities_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
Free to start. No card required.
Create multiple new entities in the project knowledge graph. It is categorised as a Write tool in the Xgmem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Xgmem 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 Xgmem. 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 Xgmem MCP server (meetdhanani17/xgmem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Xgmem, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
14 Xgmem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.