v2.1.2 Item 26: retire old_id and link to a replacement.
AI agents use supersede_decision to create or update resources in Codevira MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Codevira MCP environment.
Superseding a decision retires the old entry and establishes a replacement link. While it modifies existing records, the operation appears reversible in principle (the old record is retired/linked rather than deleted), placing it in Write rather than Destructive. However, retiring a decision that other items may depend on could have cascading effects on the knowledge base, warranting medium severity.
From the tool's definition 'retire old_id and link to a replacement' — this supersedes/retires an existing decision entry and links it to a new one
Documented attack patterns abuse exactly the kind of access supersede_decision gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Codevira MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for supersede_decision:
{
"version": "1",
"default": "deny",
"tools": {
"supersede_decision": {
"limits": [
{
"counter": "supersede_decision_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}supersede_decision 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.
v2.1.2 Item 26: retire old_id and link to a replacement. It is categorised as a Write tool in the Codevira MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Codevira MCP server in PolicyLayer and add a rule for supersede_decision: 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 Codevira MCP. Nothing to install.
supersede_decision 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 supersede_decision 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 supersede_decision. 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.
supersede_decision is provided by the Codevira MCP server (sachinshelke/codevira). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Codevira MCP, 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.
48 Codevira MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.