AI agents use create_entity to create or update resources in Memora — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Memora environment.
This is a Write category tool because it modifies data (creates or updates entities in a knowledge graph) but does so reversibly—appended data can be removed or modified through other operations like 'forget' that exist on the same server. There is no data destruction, financial impact, or code execution involved.
From the tool's definition Tool creates or modifies entities by upserting them (appends rather than replaces), which is a reversible modification operation. The description explicitly states 'Appends new observations/tags rather than replacing.'
Attacks that exploit this kind of access
Upsert an entity. Appends new observations/tags rather than replacing. It is categorised as a Write tool in the Memora MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Memora 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 Memora. 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 Memora MCP server (vnemaidev/memora). 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 →