get-all-config

Get all environment variables (returns count, keys, and a sample)

SERVERFrontmcp SOURCEagentfront/frontmcp
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/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

Questions about get-all-config

What does the get-all-config tool do? +

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.

How do I enforce a policy on get-all-config? +

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.

What risk level is get-all-config? +

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

Can I rate-limit get-all-config? +

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.

How do I block get-all-config completely? +

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.

What MCP server provides get-all-config? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Front's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.