Create an entity (person, project, decision, tool, etc.).
AI agents use entity_create to create or update resources in Jarvis Orb — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jarvis Orb environment.
Creating entities in a persistent 4-tier memory system is a Write action—it modifies the knowledge base reversibly. Severity is medium because: (1) created entities can be updated or deleted via sibling tools, (2) impact is limited to the user's memory layer, not destructive, and (3) no financial or code-execution risk. Confidence is high because the intent is unambiguous.
From the tool's definition Tool name 'entity_create' and description 'Create an entity' explicitly indicates data creation. Sibling tools include 'entity_update' and 'memory_save', confirming this server manages persistent memory structures.
Documented attack patterns abuse exactly the kind of access entity_create gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jarvis Orb, and nothing reaches the server without passing your rules. This is the rule we recommend for entity_create:
{
"version": "1",
"default": "deny",
"tools": {
"entity_create": {
"limits": [
{
"counter": "entity_create_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}entity_create 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 an entity (person, project, decision, tool, etc.). It is categorised as a Write tool in the Jarvis Orb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jarvis Orb MCP server in PolicyLayer and add a rule for entity_create: 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 Jarvis Orb. Nothing to install.
entity_create 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 entity_create 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 entity_create. 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.
entity_create is provided by the Jarvis Orb MCP server (thestack-ai/jarvis-orb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jarvis Orb, 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.
7 Jarvis Orb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.