hippo_episode_pin
FORGIA #197. Mark an episode as pinned. Pinned episodes
This record as markdown: /tools/verimem/hippo-episode-pin.md
What hippo_episode_pin does on Verimem
AI agents use hippo_episode_pin to create or update resources in Verimem, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Verimem environment.
Why hippo_episode_pin is rated Medium
This tool modifies the pinned status of an episode, which is a reversible write operation on metadata. It does not execute code, delete data, move money, or perform destructive actions. The change can be undone by unpinning.
From the tool's definition Tool description states 'Mark an episode as pinned', which is a metadata modification operation. The word 'Mark' indicates a state change to an episode record.
Attacks that exploit this kind of access
The rule that runs hippo_episode_pin 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_episode_pin, this is the rule to start with:
hippo_episode_pin 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Verimem, apply this rule, and every hippo_episode_pin call is checked against it from then on.
Questions about hippo_episode_pin
FORGIA #197. Mark an episode as pinned. Pinned episodes. It is categorised as a Write tool in the Verimem MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Verimem MCP server in PolicyLayer and add a rule for hippo_episode_pin: 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_episode_pin 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 hippo_episode_pin 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_episode_pin. 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_episode_pin 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