check-flag

Programmatically check a feature flag via this.featureFlags

SERVERFrontmcp SOURCEagentfront/frontmcp

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/frontmcp/check-flag.md

WHAT IT DOES

What check-flag does on Frontmcp

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

RISK

Why check-flag is rated Low

Checking a feature flag is a retrieval operation that determines configuration state without causing mutations, external operations, or irreversible changes. This is a classic Read category tool with minimal blast radius if misused—worst case an AI agent would observe incorrect feature states, not alter system behavior or data.

From the tool's definition The tool description states it 'check[s] a feature flag via this.featureFlags', indicating a read-only operation that queries the state of a feature flag without modifying any data or triggering side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs check-flag safely

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

check-flag Allowed

check-flag is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "check-flag": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Frontmcp, apply this rule, and every check-flag call is checked against it from then on.

FAQ

Questions about check-flag

What does the check-flag tool do? +

Programmatically check a feature flag via this.featureFlags. It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check-flag? +

Register the Front MCP server in PolicyLayer and add a rule for check-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 Frontmcp. Nothing to install.

What risk level is check-flag? +

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

Can I rate-limit check-flag? +

Yes. Add a rate_limit block to the check-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 check-flag completely? +

Set action: deny in the PolicyLayer policy for check-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 check-flag? +

check-flag is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Front, and thousands of servers like it.

This server

All 206 Front tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →