New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

evaluate_feature_flag

A read tool on the Mapi Agent Memory MCP server.

SERVERMapi Agent Memory SOURCEcabo0m/mapi-agent-memory
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/mapi-agent-memory/evaluate-feature-flag.md

What evaluate_feature_flag does on Mapi Agent Memory

AI agents call evaluate_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 evaluate_feature_flag is rated Low

Feature flag evaluation typically queries configuration state to determine which features are active, returning a boolean or flag value without side effects. No modification, deletion, code execution, or financial operations are implied. The tool fits the Read category despite the uninformative description.

From the tool's definition Tool name 'evaluate_feature_flag' suggests a query operation that retrieves the state of a feature flag configuration. The empty description limits confidence, but feature flag evaluation is inherently a read operation.

Questions about evaluate_feature_flag

What does the evaluate_feature_flag tool do? +

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

How do I enforce a policy on evaluate_feature_flag? +

Register the Mapi Agent Memory MCP server in PolicyLayer and add a rule for evaluate_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.

What risk level is evaluate_feature_flag? +

evaluate_feature_flag is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit evaluate_feature_flag? +

Yes. Add a rate_limit block to the evaluate_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.

How do I block evaluate_feature_flag completely? +

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

What MCP server provides evaluate_feature_flag? +

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

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Mapi Agent Memory's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.