config_list

List configuration values Use when native settings.json edits are wrong because the values need to be read by the Ruflo runtime (daemon, MCP server, neural router) — those load via the config_* path, not by re-reading settings.json. For .gitignore / .editorconfig style files, native Edit is fine.

Server Claude Flow claude-flow
Category Read
Risk class Low
Parameters 00 required

What config_list does on Claude Flow

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

Why config_list needs a policy

This is a straightforward read operation that retrieves existing configuration state from the Ruflo runtime. There are no side effects, no code execution, no data modification, and no destructive actions.

From the tool's definition Tool name 'config_list' and description 'List configuration values' — retrieves or queries data without modification.

Questions about config_list

What does the config_list tool do? +

List configuration values Use when native settings.json edits are wrong because the values need to be read by the Ruflo runtime (daemon, MCP server, neural router) — those load via the config_* path, not by re-reading settings.json. For .gitignore / .editorconfig style files, native Edit is fine. 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 config_list? +

Register the Claude Flow MCP server in PolicyLayer and add a rule for config_list: 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 config_list? +

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

Can I rate-limit config_list? +

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

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

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

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.