Verify, supersede, or contradict a memory. Actions: verify, supersede (old:new), contradict (a:b).
AI agents use memory_verify 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 existing memory records by verifying (marking as verified), superseding (replacing old with new), or marking contradictions between memories. These are reversible state changes to stored data, fitting the Write category.
From the tool's definition Verify, supersede, or contradict a memory. Actions: verify, supersede (old:new), contradict (a:b).
Documented attack patterns abuse exactly the kind of access memory_verify 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 memory_verify:
{
"version": "1",
"default": "deny",
"tools": {
"memory_verify": {
"limits": [
{
"counter": "memory_verify_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}memory_verify 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.
Verify, supersede, or contradict a memory. Actions: verify, supersede (old:new), contradict (a:b). 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 memory_verify: 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.
memory_verify 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 memory_verify 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 memory_verify. 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.
memory_verify 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.