AI agents use entity_update 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.
This tool modifies entity data within the memory system but does not delete or irreversibly destroy information—it updates state and maintains history, making it a Write operation. The severity is medium because uncontrolled updates to entity states in a persistent memory system could corrupt semantic relationships or project context, but the changes are tracked and theoretically reversible via history examination.
From the tool's definition Tool description states 'Update entity state' and 'Records transition history', indicating modification of existing data in a reversible manner.
Documented attack patterns abuse exactly the kind of access entity_update 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_update:
{
"version": "1",
"default": "deny",
"tools": {
"entity_update": {
"limits": [
{
"counter": "entity_update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}entity_update 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.
Update entity state. Records transition history. 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_update: 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_update 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_update 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_update. 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_update 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.