archiveFeatureFlag · Bucketeer MCP Server MCP: Risk & Policy

WHAT IT DOES

What archiveFeatureFlag does on Bucketeer MCP Server

AI agents use archiveFeatureFlag to create or update resources in Bucketeer MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bucketeer MCP Server environment.

WHY IT NEEDS A POLICY

Why archiveFeatureFlag needs a policy

Archiving is a state change operation that modifies data reversibly rather than permanently destroying it. While 'archive' might superficially resemble destructive action, the description explicitly indicates the effect is making something 'inactive' rather than deletion or permanent removal. This is a Write operation—data modification with potential to revert.

From the tool's definition Tool description states 'Archive a feature flag (make it inactive)' - archiving changes the state of a feature flag to inactive, which is a modification that is reversible (can be unarchived).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archiveFeatureFlag Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archiveFeatureFlag": {
      "limits": [
        {
          "counter": "archivefeatureflag_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Bucketeer MCP Server, so you can run agents against it safely.

FAQ

Questions about archiveFeatureFlag

What does the archiveFeatureFlag tool do? +

Archive a feature flag (make it inactive). It is categorised as a Write tool in the Bucketeer MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on archiveFeatureFlag? +

Register the Bucketeer MCP Server MCP server in PolicyLayer and add a rule for archiveFeatureFlag: 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 Bucketeer MCP Server. Nothing to install.

What risk level is archiveFeatureFlag? +

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

Can I rate-limit archiveFeatureFlag? +

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

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

archiveFeatureFlag is provided by the Bucketeer MCP Server MCP server (nnnkkk7/bucketeer-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.