config_export

Export configuration to JSON 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.

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/config-export.md

WHAT IT DOES

What config_export does on Claude Flow

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

The tool exports (reads/serializes) configuration data to JSON format. It explicitly explains when to use it versus native edits, indicating it is a read/retrieval operation. However, exported configuration may contain sensitive secrets (API keys, credentials, neural router settings), giving it medium severity if misused by an AI agent leaking that data.

From the tool's definition Export configuration to JSON — the word 'export' and the description clarifies it 'read by the Ruflo runtime', implying data retrieval without modification

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs config_export 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 config_export, this is the rule to start with:

config_export Allowed

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

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 config_export call is checked against it from then on.

FAQ

Questions about config_export

What does the config_export tool do? +

How do I enforce a policy on config_export? +

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

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

Can I rate-limit config_export? +

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

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

config_export 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

The MCP Attack Database →

Guides

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