get-all-config
Get all environment variables (returns count, keys, and a sample)
This record as markdown: /tools/frontmcp/get-all-config.md
What get-all-config does on Frontmcp
AI agents call get-all-config to retrieve information from Frontmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get-all-config is rated Low
This is a Read operation as it queries and retrieves environment variables. However, severity is elevated to 'medium' rather than 'low' because environment variables often contain sensitive information such as API keys, credentials, database connection strings, secrets, and other confidential configuration that could be exploited if exposed to an AI agent.
From the tool's definition Tool name 'get-all-config' and description 'Get all environment variables (returns count, keys, and a sample)' indicate retrieval of configuration data without modification or deletion.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs get-all-config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get-all-config, this is the rule to start with:
get-all-config 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 Frontmcp, apply this rule, and every get-all-config call is checked against it from then on.
Questions about get-all-config
Get all environment variables (returns count, keys, and a sample). It is categorised as a Read tool in the Frontmcp MCP Server, which means it retrieves data without modifying state.
Register the Front MCP server in PolicyLayer and add a rule for get-all-config: 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 Frontmcp. Nothing to install.
get-all-config 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 get-all-config 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 get-all-config. 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.
get-all-config is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
This server
Across the catalogue