list_feature_flags

What list_feature_flags does on Mapi Agent Memory

AI agents call list_feature_flags to retrieve information from Mapi Agent Memory without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_feature_flags is rated Low

The 'list' verb combined with 'feature_flags' (a read-only configuration artifact) strongly suggests data retrieval with no side effects. In an auditable governance context, listing flags would be introspectable reads. No modification, deletion, code execution, or financial impact is implied. Low severity due to the benign nature of configuration visibility.

From the tool's definition Tool name 'list_feature_flags' and the context of an auditable memory and governance system indicate this retrieves configuration state. The description is empty, limiting direct evidence, but listing operations are non-mutating queries by convention.

The rule that runs list_feature_flags 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 list_feature_flags, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_feature_flags": {}
  }
}

Questions about list_feature_flags