upsert_feature_flag
A write tool on the Mapi Agent Memory MCP server.
This record as markdown: /tools/mapi-agent-memory/upsert-feature-flag.md
What upsert_feature_flag does on Mapi Agent Memory
AI agents use upsert_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 upsert_feature_flag is rated Medium
Feature flags control application behavior and can have wide-reaching effects on system functionality when modified. While upsert is reversible (making it Write rather than Destructive), misconfiguration could disable critical features or enable unintended behaviors across an agent system, warranting medium severity.
From the tool's definition Tool name 'upsert_feature_flag' indicates insertion or update of feature flag configuration data. The 'upsert' operation (update or insert) is a reversible write operation.
Attacks that exploit this kind of access
The rule that runs upsert_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 upsert_feature_flag, this is the rule to start with:
upsert_feature_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Mapi Agent Memory, apply this rule, and every upsert_feature_flag call is checked against it from then on.
Questions about upsert_feature_flag
upsert_feature_flag is a write tool on the Mapi Agent Memory MCP server. It is categorised as a Write tool in the Mapi Agent Memory MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for upsert_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.
upsert_feature_flag is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upsert_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 upsert_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.
upsert_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