Medium Risk

reaffirm_decision

v3.2.0: refresh a do_not_revert decision

How to control reaffirm_decision ↓

What reaffirm_decision does on Codevira MCP

AI agents use reaffirm_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.

Medium Risk

Why reaffirm_decision needs a policy

This tool modifies/updates an existing decision record (refreshing its do_not_revert status) in the persistent knowledge base. It is a reversible write operation — it updates metadata rather than deleting or executing code. Misuse could cause an AI agent to lock in incorrect decisions, preventing future reverts, which raises the severity to medium.

From the tool's definition reaffirm_decision — 'refresh a do_not_revert decision'

Documented attack patterns abuse exactly the kind of access reaffirm_decision gives an agent:

How to control reaffirm_decision

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 reaffirm_decision:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reaffirm_decision": {
      "limits": [
        {
          "counter": "reaffirm_decision_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

reaffirm_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.

  1. Create a free account and register Codevira MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reaffirm_decision

What does the reaffirm_decision tool do? +

v3.2.0: refresh a do_not_revert decision. 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.

How do I enforce a policy on reaffirm_decision? +

Register the Codevira MCP server in PolicyLayer and add a rule for reaffirm_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.

What risk level is reaffirm_decision? +

reaffirm_decision is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reaffirm_decision? +

Yes. Add a rate_limit block to the reaffirm_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.

How do I block reaffirm_decision completely? +

Set action: deny in the PolicyLayer policy for reaffirm_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.

What MCP server provides reaffirm_decision? +

reaffirm_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.

Enforce policy on every Codevira MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.