Medium Risk

set_decision_flag

v3.0.0 lightweight flag/tag update for an existing decision.

How to control set_decision_flag ↓

What set_decision_flag does on Codevira MCP

AI agents use set_decision_flag 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 set_decision_flag needs a policy

This tool updates metadata (flags/tags) on decisions within the shared knowledge base, making it a Write operation. It does not delete data (not Destructive), execute code (not Execute), or process financial transactions (not Financial).

From the tool's definition The tool performs a 'flag/tag update for an existing decision,' which modifies data stored in the persistent knowledge base. 'Update' is a write operation that changes state reversibly.

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

How to control set_decision_flag

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

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

set_decision_flag 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 set_decision_flag

What does the set_decision_flag tool do? +

v3.0.0 lightweight flag/tag update for an existing 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 set_decision_flag? +

Register the Codevira MCP server in PolicyLayer and add a rule for set_decision_flag: 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 set_decision_flag? +

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

Can I rate-limit set_decision_flag? +

Yes. Add a rate_limit block to the set_decision_flag 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 set_decision_flag completely? +

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

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