AI agents use create_entity to create or update resources in Dbrain — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dbrain environment.
This tool creates new entities in the dbrain's structured memory system, which is a reversible Write operation. It does not delete, execute code, or trigger external systems. The severity is low because entity creation in a memory system has minimal blast radius—entities can be updated or the references removed without cascading damage.
From the tool's definition Tool description explicitly states 'Create a new entity' and is used 'before remembering facts about something new.' The action is creating a new data record in persistent memory.
Attacks that exploit this kind of access
Create a new entity (project, person, system, event). Use this before remembering facts about something new. It is categorised as a Write tool in the Dbrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dbrain MCP server in PolicyLayer and add a rule for create_entity: 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 Dbrain. Nothing to install.
create_entity 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_entity 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_entity. 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_entity is provided by the Dbrain MCP server (ivncmp/dbrain). 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 →