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.
AI agents call config_export to retrieve information from Ruflo without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool exports (reads out) configuration to JSON format. While it doesn't modify data, exported configurations may contain sensitive credentials, API keys, or architectural details about the multi-agent swarm system, warranting medium severity. The description focuses on reading config values loaded by the runtime, not writing or modifying them.
From the tool's definition Export configuration to JSON — the tool reads and exports configuration data; 'values need to be read by the Ruflo runtime'
Attacks that exploit this kind of access
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. 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 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 Ruflo. Nothing to install.
config_export 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 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.
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.
config_export 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.
config_export is one line of Ruflo's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →