Create multiple new entities in the knowledge graph
AI agents use create_entities to create or update resources in MCP Memory Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Memory Server environment.
This tool creates new entities in a knowledge graph, which modifies the graph structure reversibly. If misused by an agent, it could pollute the knowledge graph with incorrect or malicious entities, but the effect is reversible via deletion tools. This is characteristic of Write-category operations—data modification without permanent, irreversible consequences.
From the tool's definition Tool name: 'create_entities'; description: 'Create multiple new entities in the knowledge graph'. The verb 'create' directly indicates data creation, which is a Write operation.
Attacks that exploit this kind of access
Create multiple new entities in the knowledge graph. It is categorised as a Write tool in the MCP Memory Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Memory Server 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 MCP Memory Server. 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 MCP Memory Server MCP server (stevenwangler/mcp-memory-server). 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 →