hippo_trajectory_diff
FORGIA #282 — diff two trajectories. Returns
This record as markdown: /tools/verimem/hippo-trajectory-diff.md
What hippo_trajectory_diff does on Verimem
AI agents call hippo_trajectory_diff to retrieve information from Verimem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why hippo_trajectory_diff is rated Low
Diffing is a read-only operation that compares data structures and returns results without altering state. No data is created, modified, deleted, or executed. The tool fits the Read category: it retrieves and queries data with no side effects. Confidence is high because the operation semantics of 'diff' are well-established as non-destructive inspection.
From the tool's definition Tool name 'hippo_trajectory_diff' and description 'diff two trajectories. Returns' indicate a comparison/query operation that retrieves and displays differences between two stored trajectories without modification.
Attacks that exploit this kind of access
The rule that runs hippo_trajectory_diff safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Verimem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hippo_trajectory_diff, this is the rule to start with:
hippo_trajectory_diff is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_trajectory_diff call is checked against it from then on.
Questions about hippo_trajectory_diff
FORGIA #282 — diff two trajectories. Returns. It is categorised as a Read tool in the Verimem MCP Server, which means it retrieves data without modifying state.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_trajectory_diff: 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 Verimem. Nothing to install.
hippo_trajectory_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the hippo_trajectory_diff 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 hippo_trajectory_diff. 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.
hippo_trajectory_diff is provided by the Verimem MCP server (aureliocpr-ctrl/verimem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Verimem, and thousands of servers like it.
This server
Across the catalogue