Mark one repo-local memory packet as superseded by a replacement packet and write bidirectional lineage edges.
AI agents use kage_supersede to create or update resources in Kage — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kage environment.
This tool modifies memory state by updating packet supersession status and creating bidirectional links. While the change is reversible (packets are git-tracked JSON reviewed in PRs, allowing audit and rollback), it alters shared team memory that multiple agents and developers depend on. Misuse could corrupt knowledge lineage, creating confusion about which memory packets are current.
From the tool's definition Tool explicitly performs a write operation: 'Mark one repo-local memory packet as superseded by a replacement packet and write bidirectional lineage edges.' The verb 'write' and the act of modifying memory packet state (marking as superseded, creating lineage…
Documented attack patterns abuse exactly the kind of access kage_supersede gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kage, and nothing reaches the server without passing your rules. This is the rule we recommend for kage_supersede:
{
"version": "1",
"default": "deny",
"tools": {
"kage_supersede": {
"limits": [
{
"counter": "kage_supersede_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}kage_supersede 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.
Mark one repo-local memory packet as superseded by a replacement packet and write bidirectional lineage edges. It is categorised as a Write tool in the Kage MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kage MCP server in PolicyLayer and add a rule for kage_supersede: 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 Kage. Nothing to install.
kage_supersede 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 kage_supersede 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 kage_supersede. 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.
kage_supersede is provided by the Kage MCP server (@kage-core/kage-graph-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kage, 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.
62 Kage tools catalogued and risk-classified — across an index of 43,000+ MCP servers.