set_feature_flag

What set_feature_flag does on Mapi Agent Memory

AI agents use set_feature_flag to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.

Why set_feature_flag is rated Medium

Feature flag operations modify system configuration that affects agent behavior. This is reversible (flags can be toggled), so it falls under Write rather than Destructive. High severity due to potential to enable/disable critical agent capabilities or governance features. Confidence reduced from higher due to empty description, but the function name and server context provide sufficient basis for classification.

From the tool's definition Tool name 'set_feature_flag' indicates modification of feature flag state. While description is empty, the name and server context (auditable memory and governance for AI agents) suggest this creates or modifies configuration that controls agent behavior.

The rule that runs set_feature_flag safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For set_feature_flag, this is the rule to start with:

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

Questions about set_feature_flag