features_detect

Detect runtime features (V2 compatible). Deprecated: Use system/info instead.

SERVERClaude Flow SOURCEclaude-flow

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/io-github-ruvnet-claude-flow/features-detect.md

WHAT IT DOES

What features_detect does on Claude Flow

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

RISK

Why features_detect is rated Low

This tool performs detection and inspection of runtime features, which is a read-only operation that queries system state without side effects. The deprecation notice directing users to 'system/info' reinforces that this is an informational/diagnostic tool. No data is created, modified, deleted, or executed—only features are detected and reported.

From the tool's definition Tool name 'features_detect' and description 'Detect runtime features' indicates inspection/querying of system capabilities without modification. The tool retrieves information about runtime features.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs features_detect safely

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

features_detect Allowed

features_detect 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": {
    "features_detect": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Claude Flow, apply this rule, and every features_detect call is checked against it from then on.

FAQ

Questions about features_detect

What does the features_detect tool do? +

Detect runtime features (V2 compatible). Deprecated: Use system/info instead. It is categorised as a Read tool in the Claude Flow MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on features_detect? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for features_detect: 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 Claude Flow. Nothing to install.

What risk level is features_detect? +

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

Can I rate-limit features_detect? +

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

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

features_detect is provided by the Claude Flow MCP server (claude-flow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Flow, and thousands of servers like it.

This server

All 496 Claude Flow tools →

Across the catalogue

detect_slop on Slop Cop → The MCP Attack Database →

Guides

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