agenticow_lineage
agenticow — walk the COW chain of an .rvf memory file: an ordered list of nodes (role working|checkpoint|base, id, label, parent, createdAt, mutations, tombstones). Use when you need branch history — to find checkpoint ids for a targeted rollback, or to debug a promote. Guessing the chain from fi...
This record as markdown: /tools/ruflo/agenticow-lineage.md
What agenticow_lineage does on Ruflo
AI agents call agenticow_lineage to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why agenticow_lineage is rated Low
This tool performs a query/retrieval operation on memory file metadata to inspect version history and branching structure. It has no side effects—it only reads and returns data about the lineage chain. The highest-impact misuse would be an agent obtaining incorrect rollback targets, but the tool itself does not execute rollbacks or modify state. This is a classic Read operation.
From the tool's definition Tool description states it 'walk[s] the COW chain' to retrieve 'an ordered list of nodes' for inspection purposes. The use cases are diagnostic ('debug a promote') and informational ('find checkpoint ids').
Attacks that exploit this kind of access
The rule that runs agenticow_lineage safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agenticow_lineage, this is the rule to start with:
agenticow_lineage 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 Ruflo, apply this rule, and every agenticow_lineage call is checked against it from then on.
Questions about agenticow_lineage
agenticow — walk the COW chain of an .rvf memory file: an ordered list of nodes (role working|checkpoint|base, id, label, parent, createdAt, mutations, tombstones). Use when you need branch history — to find checkpoint ids for a targeted rollback, or to debug a promote. Guessing the chain from filenames is wrong — lineage is the authoritative structure the store maintains. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo MCP server in PolicyLayer and add a rule for agenticow_lineage: 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 Ruflo. Nothing to install.
agenticow_lineage 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 agenticow_lineage 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 agenticow_lineage. 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.
agenticow_lineage is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue