features_detect
Detect runtime features (V2 compatible). Deprecated: Use system/info instead.
This record as markdown: /tools/ruflo/features-detect.md
What features_detect does on Ruflo
AI agents call features_detect to retrieve information from Ruflo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why features_detect is rated Low
This tool retrieves information about runtime features without creating, modifying, or deleting data. It has no side effects beyond returning feature detection results. The deprecation notice suggests it's a legacy informational tool for API capability discovery, fitting the 'Read' category for data retrieval operations.
From the tool's definition Tool name 'features_detect' and description indicate it detects/queries runtime features with no modification capability.
Attacks that exploit this kind of access
The rule that runs features_detect safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, 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 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 Ruflo, apply this rule, and every features_detect call is checked against it from then on.
Questions about features_detect
Detect runtime features (V2 compatible). Deprecated: Use system/info instead. It is categorised as a Read tool in the Ruflo MCP Server, which means it retrieves data without modifying state.
Register the Ruflo 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 Ruflo. Nothing to install.
features_detect 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 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.
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.
features_detect is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue