create_entities
AI agents use create_entities to create or update resources in DAI MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your DAI MCP Server environment.
The 'create' prefix indicates this tool creates new data structures (entities) in the Neo4j graph database. This is a Write operation—reversible through corresponding delete operations. While description is empty, the name combined with server context (persistent memory storage) and presence of delete_entities sibling makes the Write categorization clear.
From the tool's definition Tool name is 'create_entities' which explicitly indicates creation of new entities. Server context describes Neo4j graph database integration for storing interconnected knowledge.
Attacks that exploit this kind of access
create_entities. It is categorised as a Write tool in the DAI MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the DAI MCP 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 DAI MCP 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 DAI MCP Server MCP server (patgpt/dai-mcp). 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 →