AI agents use entity_relate 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 the entity graph by establishing new relational connections, which is a reversible Write operation. The blast radius is medium because incorrect relationships could corrupt knowledge graph integrity or cause misclassification in downstream memory queries, but the action is not destructive (relationships can be removed) and does not execute arbitrary code or move money.
From the tool's definition Tool name 'entity_relate' and description 'Create a relationship between two entities' indicate the tool creates new data (a relationship link) without deleting or overwriting existing data.
Documented attack patterns abuse exactly the kind of access entity_relate 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_relate:
{
"version": "1",
"default": "deny",
"tools": {
"entity_relate": {
"limits": [
{
"counter": "entity_relate_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}entity_relate 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 a relationship between two entities. 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_relate: 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_relate 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_relate 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_relate. 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_relate 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.