get_feature_flag
A read tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/get-feature-flag.md
What get_feature_flag does on Mapi Agent Memory
AI agents call get_feature_flag 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 get_feature_flag is rated Low
Feature flag retrieval is a read operation that queries configuration state without side effects. The absence of a description reduces confidence slightly, but the tool name strongly indicates a safe information retrieval operation consistent with Read category. No modifications, deletions, or external execution are implied.
From the tool's definition Tool name 'get_feature_flag' indicates retrieval of configuration data. Description is empty, limiting certainty, but the naming pattern and context of an auditable memory/governance system suggests this queries feature flag state without modifications.
Attacks that exploit this kind of access
The rule that runs get_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 get_feature_flag, this is the rule to start with:
get_feature_flag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every get_feature_flag call is checked against it from then on.
Questions about get_feature_flag
get_feature_flag is a read tool on the Mapi Agent Memory MCP server. It is categorised as a Read tool in the Mapi Agent Memory MCP Server, which means it retrieves data without modifying state.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for get_feature_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 Mapi Agent Memory. Nothing to install.
get_feature_flag is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_feature_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.
Set action: deny in the PolicyLayer policy for get_feature_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.
get_feature_flag is provided by the Mapi Agent Memory MCP server (cabo0m/mapi-agent-memory). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mapi Agent Memory, and thousands of servers like it.
This server
Across the catalogue